Memory Leak caused by bouncycastle

Hi team,
We’re facing memory issues related to bouncycastle. Below are the findings after getting the dumps.  Safe to say bctls-fips components are the cause of the memory leaks in our scenario as well. It'd be appreciate if you could advise to me.
Thanks
Information related to our application:

bctls-fips <IP_ADDRESS>
bc-fips <IP_ADDRESS>
Java 17,
SpringBoot 3.1.4

Have you tried bctls 1.0.18? <IP_ADDRESS> is very out of date now.


TagBot trigger issue

This issue is used to trigger TagBot; feel free to unsubscribe.
If you haven't already, you should update your TagBot.yml to include issue comment triggers.
Please see this post on Discourse for instructions and more details.
If you'd like for me to do this for you, comment TagBot fix on this issue.
I'll open a PR within a few hours, please be patient!

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/26310

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/26625

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/26638

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/28608

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/28608

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/73083


Repeated Changed Files

Now, there are three ways to get diff code.

Crawler online: like https://github.com/cenkalti/github-flask/compare/master...tylertreat:master
My code: https://github.com/FancyCoder0/INFOX/blob/f9f0ab2e144c4eb1c1c13feff7d7255b34018f23/app/analyse/compare_changes_crawler.py

add '.patch' suffix But here is the problem that the file will be repeated(all changed history). See here: https://github.com/cenkalti/github-flask/compare/master...tylertreat:master.patch
Now it's the current version.

Use diff on local machine , not implement yet

Another problem is that to show user the location of the changed code, now only way 1 can support(link to github diff page).

Now, I output distinct elements in list.

what is the current status?

use compare_url + ".diff" , no repeat files.


Integrate new disk attach/detach API in AzCLI

Preconditions

[X] No need to upgrade Python SDK or the Python SDK is ready.

Related command
az vm disk attach
az vm disk detach
Resource Provider
Microsoft.Compute/virtualmachines
Description of Feature or Work Requested
CRP team has created a new Disk attach/detach API that customers can use to attach/detach disks to the VM. API to be used is already in public preview - Virtual Machines - Attach Detach Data Disks - REST API (Azure Compute) | Microsoft Learn
Change required in Azcli commands:

az vm disk attach - Introduce a new field --disk-ids. Customers can mention multiple disk ids after this and the API will attach all of them. Sample usage :

az vm disk attach --disk-ids <disk uri>
 [--caching {None, ReadOnly, ReadWrite}]
 [--enable-write-accelerator]<- supported
 [--lun]<- supported
 [--resource-group]
 [--subscription

az vm disk detach - Introduce a new field --disk-ids. Customers can mention multiple disk ids after this and the API will attach all of them. Sample usage :

az vm disk detach [--name]
                  --resource-group
                  --vm-name
                  [--force-detach]
                  [--disk-ids] <- new param

Minimum API Version Required
2024-03-01
Swagger PR link / SDK link
https://learn.microsoft.com/en-us/rest/api/compute/virtual-machines/attach-detach-data-disks?view=rest-compute-2024-03-01&tabs=HTTP
Request Example
No response
Target Date
2024-11-30
PM Contact
viveksingla
Engineer Contact
nij, abver
Additional context
No response

Thank you for opening this issue, we will look into it.

@viveksingla08 May I ask if this feature request is related to security? Please note that currently, due to the CLI team being busy with the security wave and prioritizing security in this semester, so all the feature requests unrelated to security will be postponed. cc PM @Jacekey23

This is related to the quality. This API would reduce the throttling faced by customers when trying to attach/detach disks

@viveksingla08 Since security is still the no.1 top things to catch up within Azure. but CLI will be in continous planning manner. If things can be justify as highly customer impact. please send the justification and we'll take it into consideration.


Issue#2641. Added E-book section

Related Issue
#2641
Description
I have added the E-book section with 4 sample books.
Type of PR

[x] Feature enhancement

Screenshots / Videos (if applicable)

Checklist

[x] I have performed a self-review of my code.
[x] I have read and followed the Contribution Guidelines.
[x] I have tested the changes thoroughly before submitting this pull request.
[x] I have provided relevant issue numbers, screenshots, and videos after making the changes.
[x] I have commented my code, particularly in hard-to-understand areas.
[x] I have followed the code style guidelines of this project.
[x] I have checked for any existing open issues that my pull request may address.
[x] I have ensured that my changes do not break any existing functionality.
[x] Each contributor is allowed to create a maximum of 4 issues per day. This helps us manage and address issues efficiently.
[x] I have read the resources for guidance listed below.
[x] I have followed security best practices in my code changes.

Additional Context
[Include any additional information or context that might be helpful for reviewers.]
Resources for Guidance
Please read the following resources before submitting your contribution:

[ ] Code Harbor Hub Community Features
[ ] Docusaurus Documentation
[ ] React.js Documentation
[ ] Markdown Guide
[ ] MDX Documentation
[ ] Mermaid Documentation

Resources for DSA Features on Our Site:

[ ] Tabs: Switch Languages
[ ] Line Numbering
[ ] Math Equations

Contribution Guidelines
Thank you for considering contributing to our project! To ensure smooth collaboration and effective contribution management, please adhere to the following guidelines:
Issue Creation

Limit on Issues:

Each contributor is allowed to create a maximum of 4 issues per day. This helps us manage and address issues efficiently.

Contribution Levels

Basic Contributions:

This project is primarily focused on documentation. Most of the setup has been completed, so contributors will generally need to work on basic code tasks, such as writing tests.
For these tasks, issues will be assigned the level1 label.

Acknowledging Hard Work:

If a contributor puts in significant effort on a task, the issue will be upgraded to level2. This is our way of recognizing and appreciating extra effort.

Feature Additions and Component Work:

Contributors working on new features or components using JSX/TSX will be assigned a level based on the complexity and quality of their work.
The more complex and valuable the contribution, the higher the level assigned.

Level Definitions

Level1:

Tasks are straightforward, such as fixing minor bugs, writing tests, or making simple documentation updates.

Level2:

Tasks require more effort, such as addressing complex bugs, improving existing features, or making substantial documentation improvements.

Level3:

Tasks are highly complex and involve significant new feature development, major refactoring, or extensive contributions to the project’s core components.

We look forward to your contributions and appreciate your effort in helping us improve the project!

@Ajay-Dhangar I did not understand the checks properly. Please tell me what I should do to solve these al though the PR has no conflicts with the base branch


Add C++/WinRT cross-link to C++/CX migration page

@stevewhims : PR passed PR acceptance checklist. Please evaluate further and approve/merge if appropriate. Thanks!

This topic is a topic in the C++/WinRT section of the docs. It's not a topic in the C++/CX docset, hence I included a link to the C++/CX docsset. Is the intent of this PR to solve the issue of folks having dropped into this topic, and finding themselves in need of an "Intro to C++/WinRT" topic:? If so, then solving that problem properly would involve replacing every occurrence of the string "C++/WinRT" in the C++/WinRT docs with a hyperlink to the "Intro to C++/WinRT" topic. Which feels very wrong to me. Hence, it feels wrong in this special case. Once a reader lands on this topic, or any of its siblings in the C++/WinRT docs, the table of contents in the browser shows them what topics are available, including the Intro topic. That feels like the solution. If I mentioned "C++/WinRT" outside the context of the C++/WinRT docs, then I link to the index page.

@stevewhims I appreciate that reasoning. I added the crosslink for exactly the reason you mentioned.
I'm used to following the Wikipedia style for this, where the first instance of key words should be linked, no matter what. I think the table of contents is a good mitigator, but I think that cross-links are generally helpful. Of course, that's a decision for y'all on the content teams :)
I'm happy with a decision either way. Thanks!

I see! I'll probably make the change you suggest to every first occurrence of "C++/WinRT" on every topic within the docset except the Intro topic itself. A lot of our topics link to themselves, which is a mistake IMO (since clicking the link is a confusing no-op for the reader), and this felt close in spirit to that, but I can see that it isn't. :) Oh, and I won't make the change to this particular topic, as I've now renamed the file so this PR won't succeed in any case. Please keep the suggestions coming, but if you could add your reasoning (or even email me directly), that'll make the intent clearer for me. Thanks! ~Steve

Thank you for listening! I'm happy to keep sending feedback 😁.

Great, thanks, Ben. I'll close this one, then. :)


Features/views

🚀 Feature: Beautifully Crafted Front-End Implementation
An Aesthetic Journey
We're delighted to present this PR, a testament to our commitment to an exquisite front-end implementation. We've poured our hearts into translating the wireframes into a user-friendly and functional design. While styling is indeed a nice-to-have, our primary focus has been on ensuring that every element functions seamlessly.
The Design Masterpiece
🎨 Wireframe Implementation

With unwavering determination, we've meticulously implemented the design as portrayed in the enchanting sneak peek wireframes.
Every pixel and element has been thoughtfully placed to create an intuitive user experience.

🔎 Deep Analysis

We embarked on a profound exploration of the wireframes, dissecting each element to ensure a user-friendly journey from one page to another.
Our focus was to make navigation seamless and delightful.

🔮 Data Processing Wizardry

Leveraging the robust methods we've created in the Blog App, we've breathed life into the interface, ensuring that the data dances harmoniously with the design.
Our database is now adorned with posts and comments, making the experience more engaging.

A Visual Symphony
🖌 Styling Elegance

While styling was a secondary consideration, we've sprinkled a touch of elegance into the interface, offering a visual symphony to complement the functionality.
The harmony between aesthetics and utility is our aspiration.

📄 Collaboration and Documentation

This PR is a testament to our devotion to creating a delightful user experience. It has been prepared for your esteemed review and contemplation.
The documentation is a succinct overview of the changes made and the profound purpose of this pull request.

Reviewer's Eye for Beauty
We extend our humble request to the discerning code reviewer to explore our front-end masterpiece. The journey from wireframes to a functional design has been our quest, and your insights on the aesthetics and usability are highly valued. Thank you for your aesthetic sensibility in reviewing this PR.

Thank you for your valuable review and approval. @Abenezer-Tilahun


Disable video recording in Windows due to ffmpeg crash

Description
Disable video recording in Windows due to ffmpeg crash
Also remove a rm issue causing failure due to file not exist.
Issues Resolved
https://github.com/opensearch-project/opensearch-dashboards-functional-test/issues/1068
Check List

[x] Commits are signed per the DCO using --signoff

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

Is the picture uploading still working? Just want to make sure that it still has some traces for developers to debug

Is the picture uploading still working? Just want to make sure that it still has some traces for developers to debug

This only disable the video recording, did not touch the picture functionality.


Feature request: Save embeddings, multiple files

This is a feature request for saving the embeddings.
Idea is to not to re-iterate the process of getting embeddings every time.
Also allow chats with multiple files... all of them kept saved.

let me know if anyone finds an optimal solution for storing the embeddings


[3.x] Fix incompatible addition in auto exposure shader

After turning on auto exposure on my Android device, it produces a shader compilation error:
E 0:00:02.057   _display_error_with_code: ExposureShaderGLES3: Fragment Program Compilation Failed:
ERROR: 0:38: '+' :  wrong operand types  no operation '+' exists that takes a left-hand operand of type '2-component vector of float' and a right operand of type 'const 2-component vector of int' (or there is no acceptable conversion)
ERROR: 1 compilation errors.  No code generated.

It complains about gl_FragCoord.xy + ivec2(1) operands being incompatible, and auto exposure fails to work even if I change framebuffer allocation type to 3D.

Thanks!

Cherry-picked for 3.4.1.


Returning boolean value

Added creating functions which can return boolean values

[x] I have read freeCodeCamp's contribution guidelines.
[x] My pull request has a descriptive title (not a vague title like Update index.md)
[x] My pull request targets the master branch of freeCodeCamp.
[x] None of my changes are plagiarized from another source without proper attribution.
[x] My article does not contain shortened URLs or affiliate links.

If your pull request closes a GitHub issue, replace the XXXXX below with the issue number.
Closes #XXXXX

Hactober Fest :)

Thank you for opening this pull request.
This is a standard message notifying you that we’ve reviewed your pull request and have decided not to merge it. We would welcome future pull requests from you.
Thank you and happy coding.


New Prettier+ESLint+EditorConfig setup. h/t @filoozom

Proposed replacement of StandardJS/JSLint in VS Code with Prettier + ESLint + EditorConfig.
See the development section of the README.md for info and which plugins you should install. You should disable the existing plugins for linting and code formatting for this project.
Once we shake out any issues here this config would be intended to be applied across all repositories.
This can be configured to run source code re-formatting on save of file with the following entry in VSCode user prefs:
{
...
  "eslint.autoFixOnSave": true
...
}

See:
https://eslint.org/
https://prettier.io/
https://editorconfig.org/

Hat tip to @filoozom for starting the discussion on this and opening PR #15.

Don't forget to add a pre-commit hook that fixes files before commiting to make sure that the code is correct for developers that don't use VS Code or don't have the right plugins installed. With husky and lint-staged for example. 😉


Write meta attribute as JSON into the derivation

This allows to generate SBOMs and filter derivations based on license without relying on evaluation time information.
The downside is that changing meta attributes triggers a rebuild (which shouldn't have much impact with CA derivations).
Another downside is disk space usage, for example pkgs.git closure of .drv files goes from 3.8MB to 4.4MB.
This is part of a larger effort to bring security vulnerability notifications to https://cachix.org and anyone else that wants to have the automation.

which shouldn't have much impact with CA derivations

Aren't CA derivations still an experimental feature? We can't rely on them like this.
Metadata changes should not cause rebuilds and should not be part of the output. That's not metadata, that's data. If the maintainers of glibc change we shouldn't rebuild the world. The proper fix here is for Nix to have some mechanism for attaching metadata to store objects that doesn't impact the hash algorithm.

If this feature is important, implement it properly in Nix. No need to wait for CA derivations.

If this feature is important, implement it properly in Nix. No need to wait for CA derivations.

I like to split improvements into three phases:

make it work (here comes the benefit)
make it correct (fix the bugs)
make it fast (CA derivations / Nix allowing derivation inputs not impacting hashing)

You're "making it work" by breaking the semantics of an existing working system for everyone. You're not building some prototype of some opt-in functionality. Again, why not do your step 1 by implementing a prototype of a metadata feature in Nix? In 30 seconds of thought here's an approach you could probably put together in a day or two:

Add a field to the db for metadata, just an arbitrary string optionally associated with any store path
Add a new builtin configurableDerivationStrict that takes a set containing { meta, drvArgs }, passes drvArgs to derivationStrict, and attaches meta to the .drv storepath
Have mkDerivation use configurableDerivationStrict if Nix supports it and there is metadata.

You're "making it work" by breaking the semantics of an existing working system for everyone. You're not building some prototype of some opt-in functionality. Again, why not do your step 1 by implementing a prototype of a metadata feature in Nix? In 30 seconds of thought here's an approach you could probably put together in a day or two:

Add a field to the db for metadata, just an arbitrary string optionally associated with any store path
Add a new builtin configurableDerivationStrict that takes a set containing { meta, drvArgs }, passes drvArgs to derivationStrict, and attaches meta to the .drv storepath
Have mkDerivation use configurableDerivationStrict if Nix supports it and there is metadata.

I'm not sure creating another type of derivation is the right approach here, given that this is a solved problem already as experimental feature in Nix for ~2 years.

I'm not sure creating another type of derivation is the right approach here, given that this is a solved problem already as experimental feature in Nix for ~2 years.

I'm not creating another type of derivation. I'm suggesting simply a wrapper primop that adds a new field to the Nix db.
Do CA derivations work? Are they ready to be enabled by default? Are they stable? If so, then they should be unexperimental. If not, they cannot be relied upon. Even if they were non-experimental, they would not be a proper solution here: nothing should rebuild if you change metadata.

Note that your suggestion breaks most likely the semantics of .drv files if I understand it correctly, for example for existing parsers.

No, no data is stored in the drv. Just in the db associated with the drv path.

Or maybe even keep it in "source" derivations and not in "package" derivations.

Given the package drv, we can almost always identify the src, unpack it, and scan the result for licenses. No new drv needed, probably gets you 95% coverage with a simple script. Seems like a perfect fit for @domenkozar's "make it work" stage.

identify the src, unpack it, and scan the result for licenses

I think this is too much effort with a bunch of corner cases, so “caching” the result of such action is a good thing. I also understand the need for having this cached not just in code, but in derivations as often you don’t have sources for drvs that produced these outputs, but drvs themselves are quite easy to keep around with keep-derivations.

identify the src, unpack it, and scan the result for licenses

I think this is too much effort with a bunch of corner cases, so “caching” the result of such action is a good thing.

That's exactly what IFD can already do today. Just because it doesn't fly with Hydra and its scheduler doesn't mean it's a bad idea - meta isn't recursed AFAIK anyways. I still would very much prefer if we specified this stuff manually, rather than blindly trusting a script to gather the right data.

I've changed the implementation to be opt-in, so that we can develop the feature until it's ready to be on by default.

Do CA derivations work? Are they ready to be enabled by default?

No, they are far from ready. At the moment you can't reliable convert a already built system output because each other referencing outputs create deadlocks. In the past multiple such deadlocks where already fixed but I can easily imagine that there are more to be found and edge cases to be fixed.
Also hydra support is not existing and the open PR for it is stale and I couldn't get it work.

This could be handled by improving the string context mechanism. That way we don't "pollute" the drv files.

https://github.com/NixOS/nix/issues/4677

After Domen posted this PR in #slsa:nixos.org a quick exploratory discussion enaued between @RaitoBezarius and myself the outcome of which I want to resume here:

More than a question of metadata storage, it can be considered a question of cache storage (since the SBOM data will be reproducible)

That renders the question addressed by this PR one of a cache storage implementation

.drv for the reasons mentioned above and also from its principle design as "build recipes", may be a very unsuitable implementation of such a cache

other options to implement such a cache would be:

the local cache in the sql database, as proposed by @shlevy
a remote cache, i.e. sbom.cachix.org / sbom.nixos.org

Using .drv as a cache implementation still seemed unsuitable to us even if in practical terms, using it could lead to a quick "make it work" improvement of ecosystem outcomes (potentially improving security).
The reasons it seemed unsuitable even when compared against the very desirable potential gain in function cited in this PR mostly stems from:

.drv was not designed to be a cache layer / metadata transport layer even if placing something into a drv has all the effects of a cache via Nix' build cache
this may set a precedent that can lead the community in the wrong architectural direction from which it may be difficult to recover. Would we have the governance to follow up and correct the implementation and ensure proper migration? Wouldn't it create lock-in costs that are hard to overcome? We answered those questions in favor of not setting this precedent, but we also did not validate for other existing precedents.
an independent (metadata) cache layer implementation may emerge in a sandbox (whether remote or in sqlight) to validate all assumptions and use cases and a later settling inside Nix or Nixpkgs is a suitable path forward

I hope I did capture the outcomes appropriatly and that our findings are well received.

https://github.com/NixOS/nix/pull/8080 is somewhat related; the approach currently implemented there only applies metadata from build outputs, but I could see a future where tags can come from evaluation-time info that doesn't land in the derivations.

Can't we just have mkDerivation in Nixpkgs write another file with the metadata which refers to the derivation?

I'll mark this as draft, as it's clear this shouldn't be merged until multiple concerns are resolved, and I want to prevent this getting merged by someone by accident (well aware there is currently a merge conflict, that prevents it from being merged right now anyway).

I'm still thinking about this because it seems like such low-hanging fruit.
Storing the meta.license attribute would get us 90% there, create almost no rebuild past the initial one, and limit the size growth of the .drv. It seems such an obvious trade to me.
The proposed alternatives are interesting but require patching Nix, changing the binary cache protocol, or deploying new infrastructure. These ideas require one or two orders of magnitude more effort to get out there, and so far, I haven't seen anybody decide to tackle them.
This is the typical "perfect is the enemy of good" situation; everybody jumps in with their ideal opinions. Now, almost one year later, nothing happens. We could have benefited from the hacky solution already.

Agreeing with you @zimbatm. I'd be fine with merging this in principle, but I'd like to see:

Since this is clearly not something internal, we should have documentation and tests
We should either mark this as experimental, to reserve the right to change it in the future, give some more thought on what the interface should be, and/or make sure the interface can be evolved in the future. In particular, it might make more sense to always give the licenses as a list of SPDX identifiers, instead of the somewhat arbitrary format of meta.license.

Please be aware the this is how bad design choices and complexity proliferate. Slippery slope and all that.
I'd much prefer that people work on solving root causes.
That said, a non-mass-rebuild solution such as https://github.com/NixOS/nix/issues/10780 is not available, and Nixpkgs can make its own choices.
Let's make sure we mitigate the impact of this workaround and make sure we actually agree, specifically:

@domenkozar, please only store the license. This is about SBOM and we probably still don't want the more frequent changes to maintainers, description, etc to have to go through staging.

@alyssais, since you are the code owner of /lib/licenses.nix, your work will be affected, as more changes to package licensing and/or the general licensing infrastructure will have to go through staging. Are you ok with this?

I have more urgent matters to do, would be great if someone picks this up.

@alyssais, since you are the code owner of /lib/licenses.nix, your work will be affected, as more changes to package licensing and/or the general licensing infrastructure will have to go through staging. Are you ok with this?

That's fine by me.  There's a lot to improve about licenses.nix, but that work isn't exactly happening fast, so it's fine for it to go through staging.  I wouldn't want to commit to the format of licenses in drv files being stable though, unless all that's written is a SPDX identifier.


Update to LICENSE and NOTICE per LYRASIS merger

This PR includes small updates to the DSpace LICENSE and NOTICE files per the DuraSpace merger with LYRASIS.
No code changes here, just wanted to ensure these changes were documented in a PR.  Additionally, this will need backporting to other active branches (6.x, 5.x, etc)

Merging as this is updates to the LICENSE and NOTICE only.

This update was cherry-picked & pushed to both 5.x and 6.x:

6.x commit: https://github.com/DSpace/DSpace/commit/f81b8ce9491466f412eef3b0eb76c1d74d8df527
5.x commit: https://github.com/DSpace/DSpace/commit/f93f371b21e41a13fcd7b991888e8eda56c3146b


message: Respect first_visible_message_id when computing unreads.

This prevents unread counts for messages which the web UI does not display, and does not let you mark as unread via "mark all as read."

So this is surely an improvement, but I had the realization that because the cutoff is mutable, it presumably is the case that you'll load the Zulip web app with a given first unread message ID, and then the next day, you'll have less access, and so some unreads might still not be accessible.

...if the old messages are in the cache they might be accessible, since we don't force them out in any way, we just negrect to provide them when fetching a narrow, right?
So I think this is a strict improvement but there's a big can of worms at the bottom of this in general.


Consider using json5 parser for turbo.json

Describe the feature you'd like to request
I would like to add inline comments to the turbo.json file to explain somethings for later reference
Describe the solution you'd like
Switch to a json5 parser in Go which supports comments, e.g. https://github.com/barney-ci/go-json5?ref=golangexample.com
Describe alternatives you've considered
Not use comments

I am happy to make a PR for this when this idea is accepted


Fix packer instructions typo in README.md

Thanks, change commit name to docs: fix packer instructions typo in README.md then we can merge this @qgadrian


Feature/navigate style

Andrew, I added the element we discussed. I need to do a bunch of work to make sure it looks right across different devices, but this should be enough of a starting point so you're not blocked.

The commit log is weird here. I'd either rebase this branch against develop, and then force push this branch, or create a new branch, cherry pick your commit onto it, and then submit that branch as a new PR.
Preference to option 1, if you're unsure, chat me and I can help out!

Not sure what happened there! Just rebased against develop.

nice +1


Specify namespace in examples

Perhaps the namespace was left off for brevity, but I think it's useful for new users to have an example that's easy to play around with.

@andyw8 Thanks Andy for your contribution. :) We are merging pull request in. Is the gem working well for you?


Add error boundaries to avoid white screen of death

Design guidelines — see the June 2019 prototype, section 1 (Error messages for browser support).
What‘s included
This PR adds the ErrorBoundary component that is intended to stop the errors that may occur during rendering of a component from propagating further up the React component tree (because if the error reaches the top React node the whole child DOM tree will be unmounted, which will result in the entirely empty screen ("white screen of death").
The ErrorBoundary component receives a fallback component as a prop, and will show this fallback component if rendering of its children produced an error. This PR adds two fallback components: one (called NewTechError) to use for the parts of the site where we are relying on new technology (such as web assembly) and expect that some browsers will fail to show these components. The other fallback component (called GeneralErrorScreen) is the ultimate fallback for when something entirely unpredictable happens.
What‘s not included
When the error boundary catches an error, it should report this error to an error monitoring service. This PR adds the error-service file to define the interface for reporting errors, but since we have not yet chosen an error monitoring service, this file isn't doing anything particularly useful at the moment.

Unless @msmanoj wants some some changes to be made, I think this is good to be merged into dev.


Add Python 3.10 to supported versions

Codecov Report

Merging #60 (cfb710a) into main (43e992d) will not change coverage.
The diff coverage is n/a.

:exclamation: Current head cfb710a differs from pull request most recent head b5589e8. Consider uploading reports for the commit b5589e8 to get more accurate results

@@            Coverage Diff            @@
##              main       #60   +/-   ##
=========================================
  Coverage   100.00%   100.00%
=========================================
  Files           15        15
  Lines          738       736    -2
=========================================
- Hits           738       736    -2

Impacted Files
Coverage Δ

meilisearch_python_async/index.py
100.00% <0.00%> (ø)

meilisearch_python_async/decorators.py
100.00% <0.00%> (ø)

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 43e992d...b5589e8. Read the comment docs.


ci: k8s deployment files

Acknowledging that we ended up destroying the github verification of some of the commits along the way, but are merging anyhow after careful review.


Nested RecyclerView

hi
i have nested horizontal recyclerview in row holder but inner recyclerview cannot scroll horizontally because swipe action started
i have implemented this recyclerview
https://github.com/h6ah4i/RecyclerViewiOSMailAppLikeSwipe

i resolve this problem by this answer https://github.com/h6ah4i/android-advancedrecyclerview/issues/144
but nested horizontal recyclerview can't swip and drag pleas help me


Documentation request: Recommended solutions for static cache invalidation

It's a good idea to create immutable static assets, such as images, and set the cache to never expire. It appears that Next.js does a good job of this for the JavaScript files, but it would be great to document a solution for CDN static assets.

[x] I have searched the issues of this repository and believe that this is not a duplicate.

Expected Behavior

Next.js build assets get served from _next/<some uuid>/<asset path>. Perhaps a similar solution could work for static assets as well? We could supply instructions for setting up common reverse proxies to serve the static assets properly (nginx, haproxy).
Current Behavior

Static assets always get served from the same URL, which forces users to roll their own cache-invalidation solution for static content, even though perfectly usable cache-invalidation is already built-in to Next.js.
Context

We recently rolled a new version of one of our apps into production. Everything worked great, but it served up the old image assets, which may cause a lot of confusion.
Presumably, a solution to this problem is needed for every application ever made. We should make sure it's covered in the Next.js documentation.
Your Environment
No bug. Just requesting documentation.

I wonder if you could use a custom webpack config with the file-loader and add a hash to do this?
https://webpack.js.org/loaders/file-loader/
Haven't tried this. Might give this a quick go on Monday morning.

@sergiodxa made an example: https://github.com/zeit/next.js/tree/canary/examples/with-hashed-statics


os: Test{Read,Write}TimeoutFluctuation failures on BSD variants

--- FAIL: TestReadTimeoutFluctuation (1.04s)
    timeout_test.go:272: Read took over 1s; expected 0.1s
--- FAIL: TestWriteTimeoutFluctuation (1.06s)
    timeout_test.go:324: Write took over 1s; expected 0.1s
FAIL
FAIL	os	1.975s

greplogs --dashboard -md -l -e '(?ms)FAIL: Test(?:Read|Write)TimeoutFluctuation.*FAIL\s+os\s' --since=2021-01-01
2022-01-18T23:59:40-50869f3/dragonfly-amd64
2021-11-18T06:05:29-f6647f2/freebsd-arm-paulzhol
2021-11-03T00:07:03-d6f7203/dragonfly-amd64
2021-09-24T14:52:47-217507e/netbsd-arm-bsiegert
2021-09-21T20:28:50-2fc7df9/dragonfly-amd64
2021-04-16T01:54:27-f08c552/dragonfly-amd64-5_8
This may or may not be related in some way to #50189.
The most frequent recent failures are on dragonfly-amd64 (CC @tuxillo). A good first step might be to change the test to panic instead of calling t.Errorf or t.Fatalf: a panic would at least dump any goroutines that are stuck so that we can see which goroutines and/or system calls are still in flight at the time of failure.

greplogs -l -e '(?ms)FAIL: Test(?:Read|Write)TimeoutFluctuation.*FAIL\s+os\s' --since=2022-01-19
2022-05-06T17:41:30-091e913/dragonfly-amd64

I still think changing the test to panic would be a good first step — it would be nice to know what the test is blocked on when it fails!

Okay, let me know if we need to check anything OS specific on our side :)

Rolling forward to 1.20.  Please comment if you disagree.  Thanks.

Another failure on https://storage.googleapis.com/go-build-log/6db3b12e/openbsd-amd64-68_317a0f16.log (an openbsd-amd64-68 TryBot)
If we're not going to prioritize a fix for these tests, they should be skipped to reduce noise when testing unrelated changes.

An 0.9s delay during all.bash on a slow machine (running many different test binaries at once, which can be causing long rescheduling delays) does not seem out of the ordinary to me. I think this test is too picky.

(Note that that fix also needed a followup in CL 372215.)

I will prepare a CL.


how to improve the speed of  spi communication?

I ran the "spi_loop.c " to get data from ad7606, the frequency is 3khz. But i need more than 20khz, Is there other method to improve the spi communication speed?
here is my modified code of SPI_loop.c：
//gcc -Wall -o spi_loop spi_loop.c -ljetgpio
//sudo ./spi_loop
#include <stdio.h>
#include <stdint.h>
#include <stdlib.h>
#include <unistd.h>
#include <string.h>
#include <jetgpio.h>
#include <time.h>
struct timespec start, end;
double elapsed_time;
void ADC7606_Reset()
{
gpioWrite(16, 1);
gpioWrite(16, 0);
}
void Convert_Volt(uint16_t* input, float* output, int inputSize) {
const float lsb_voltage = 5.0f / 32768.0f;
for (int i = 0; i < inputSize; i++) {
    int16_t signedInput = (int16_t)input[i];
    if (input[i] > 32767) {
        signedInput = (int16_t)(input[i] - 65536);
    }
    output[i] = signedInput * lsb_voltage;
}

}
int main(int argc, char *argv[])
{
int Init;
int SPI_init;
int SPI_stat;
uint16_t tx[4] = {0,};
uint16_t rx[4] = {0,};
float voltages[4] = {0};
Init = gpioInitialise();
if (Init < 0)
{
    printf("Jetgpio initialisation failed. Error code: %d\n", Init);
    return EXIT_FAILURE;
}
else
{
    printf("Jetgpio initialisation OK. Return code: %d\n", Init);
}

gpioSetMode(15, JET_OUTPUT);
gpioSetMode(16, JET_OUTPUT);
gpioSetMode(18, JET_INPUT);

SPI_init = spiOpen(0, 50000000, 0, 0, 16, 0, 1);
if (SPI_init < 0)
{
    printf("Port SPI1 opening failed. Error code: %d\n", SPI_init);
    return EXIT_FAILURE;
}
else
{
    printf("Port SPI1 opened OK. Return code: %d\n", SPI_init);
}

ADC7606_Reset();

while (1)
{
    clock_gettime(CLOCK_MONOTONIC, &start);
    gpioWrite(15, 1);
    gpioWrite(15, 0);
    while(gpioRead(18) == 0)
    {}
    gpioWrite(24, 0);
    SPI_stat = spiXfer(SPI_init, (char*)tx, (char*)rx, 8 * sizeof(uint16_t));
    if (SPI_stat < 0)
    {
        printf("SPI port transfer failed. Error code: %d\n", SPI_stat);
        break;
    }
    gpioWrite(24, 1);
    clock_gettime(CLOCK_MONOTONIC, &end);

    elapsed_time = (end.tv_sec - start.tv_sec) * 1e9;
    elapsed_time = (elapsed_time + (end.tv_nsec - start.tv_nsec)) * 1e-9;

    printf("Elapsed time: %f seconds\n", elapsed_time);

    printf("Data received:\n");
    for (int j = 0; j < 4; j++) {
        printf("tx%d:%x --> rx%d:%x\n", j+1, tx[j], j+1, rx[j]);
    }

    Convert_Volt(rx, voltages, 4);

    for (int i = 0; i < 4; i++) {
        printf("Channel %d: %f V\n", i+1, voltages[i]);
    }

    memset(rx, 0, sizeof(rx));
}

spiClose(SPI_init);
gpioTerminate();
return EXIT_SUCCESS;

}

Cheers @SalmanKhaja, that's quite right.
OK @Hubuwenxin I will try to help a bit but remember that whatever I say is based only on the datasheet.
So the timing diagrams are:

and for SPI:

So looking at then we would need the following pins (aside from SPI):

RESET (you are using pin 16)
CS (looks like you are using 24)-> you don't need to do: gpioWrite(24, X) , you can remove both lines, the SPI function will take care of the CS pin, pin 24 is CS0 on the AGX, you still can use another pin but in that case you have to do a: gpioSetMode(XX, JET_OUTPUT) previously
CONVST A(you are using pin 15)
BUSY(you are using pin 18 as input)

Your bottleneck is waiting for BUSY I guess? ->  while(gpioRead(18) == 0) {}
I see something weird here, BUSY is 1 during conversion but you are waiting while 0? it should be:
while(gpioRead(18)){}
You could try to change that, see what happens?

From your code, I can see that you have configured SPI at 50MHz
SPI_init = spiOpen(0, 50000000, 0, 0, 16, 0, 1);
I think, you are confused about the sampling rate of your ADC with SPI speed.

reply: yes, actually the max frequency of ADC is more than 20MHz, and agx orin is  50Mhz,  but when using spi to transmit the data from adc to agx orin  is very slow, just 3khz. And i tested adc with MCU(stm32) up to 40khz, but connect MCU to agx orin is also slow.
So i think maybe the agx part decrease the transmit frequency.

Cheers @SalmanKhaja, that's quite right. OK @Hubuwenxin I will try to help a bit but remember that whatever I say is based only on the datasheet.
So the timing diagrams are:

and for SPI:

So looking at then we would need the following pins (aside from SPI):

RESET (you are using pin 16)
CS (looks like you are using 24)-> you don't need to do: gpioWrite(24, X) , you can remove both lines, the SPI function will take care of the CS pin, pin 24 is CS0 on the AGX, you still can use another pin but in that case you have to do a: gpioSetMode(XX, JET_OUTPUT) previously
CONVST A(you are using pin 15)
BUSY(you are using pin 18 as input)

You are waiting for BUSY I guess? -> while(gpioRead(18) == 0) {} I see something weird here, BUSY is 1 during conversion but you are waiting while 0? it should be: while(gpioRead(18)){} ?
You could try to change that? You could also could remove that while() altogether and just read all the time? is more or less what you are doing now. Also, I would remove the printfs() as well, dump the values on a file for 10 s or something and measure the time at the beginning and at the end and calculate the samples/ second there.

I follow your suggestion and it help improve the speed, but  still far from 20KHz.

@Hubuwenxin
You are right, I tried on the Orin AGX and the same result with Orin Nano, the number of samples/transfers per seconds is just above 3000, really low. I tried in the old Nano and I am getting over 23000...
I really don't know the reason for this one, but there is some problem going on for the Orin family and the SPI I don't have a solution for this at this time.

For documentation purposes only, the SPI driver is introducing  a massive delay for all Jetpacks from 5.1.2 at least, this affects the whole Orin family, driver is the same. I verified this, latest 6 doesn't seem to solve the problem. Haven't tried to go back to 5.1.1.
https://forums.developer.nvidia.com/t/spi-ioc-message-ioctl-for-spi-extremely-slow/295460

@Hubuwenxin
You are right, I tried on the Orin AGX and the same result with Orin Nano, the number of samples/transfers per seconds is just above 3000, really low. I tried in the old Nano and I am getting over 23000...
I really don't know the reason for this one, but there is some problem going on for the Orin family and the SPI I don't have a solution for this at this time.

I tried the connect the ad7606 with agx by parallel mode , but the problem is that 16 gpio pins of the agx orin don't change. I tested every pins, and many pins can get 0 and 1  as  input. so i not sure that is the agx orin problem or else?

@Hubuwenxin  can you show me your code here please?

here is the parallel code:
#include <stdio.h>
#include <stdlib.h>
#include <unistd.h>
#include <time.h>
#include <jetgpio.h>
// Giving meaningful names to pins in the Orin
#define CS_RD 37
#define CONVST_AB 7
#define BUSY 38
#define RESET 36
#define DB0 10
#define DB1 11
#define DB2 12
#define DB3 13
#define DB4 15
#define DB5 16
#define DB6 18
#define DB7 19
#define DB8 21
#define DB9 22
#define DB10 23
#define DB11 24
#define DB12 26
#define DB13 29
#define DB14 31
#define DB15 32
#define BILLION<PHONE_NUMBER>L
#define NUM_CHANNELS 4
uint64_t diff;
struct timespec start, end;
void ADC7606_Reset() {
gpioWrite(RESET, 1);
usleep(10); // Ensure the reset pulse is long enough
gpioWrite(RESET, 0);
}
void Convert_Volt(const uint16_t* input, float* output, int inputSize, float xferFactor) {
for (int i = 0; i < inputSize; i++) {
int16_t signedInput = (int16_t)input[i];
if (input[i] > 32767) {
signedInput = (int16_t)(input[i] - 65536);
}
output[i] = signedInput * xferFactor;
}
}
int main(void) {
uint16_t Vx[NUM_CHANNELS] = {0};
//int pin_level[16] = {0};
float voltages[NUM_CHANNELS] = {0};
int Init = 0;
const float inputRange = 5.0f;  // Adjust based on your ADC configuration
const float xferFactor = inputRange / 32768.0f;
double elapsed_seconds = 0;  // Changed to double
// List of AGX data pins DB0 to DB15
unsigned pin_number[16] = {DB0, DB1, DB2, DB3, DB4, DB5, DB6, DB7, DB8, DB9, DB10, DB11, DB12, DB13, DB14, DB15};
Init = gpioInitialise();
if (Init < 0)
{
    /* jetgpio initialisation failed */
    printf("Jetgpio initialisation failed. Error code: %d\n", Init);
    exit(Init);
}
else
{
    /* jetgpio initialised okay */
    printf("Jetgpio initialisation OK. Return code: %d\n", Init);
}

// Setting BUSY and data pins as inputs
for (unsigned i = 0; i < 16; i++) {
    gpioSetMode(pin_number[i], JET_INPUT);
}
gpioSetMode(BUSY, JET_INPUT);

// Setting CS/RD and CONVSTA & B as outputs
gpioSetMode(CS_RD, JET_OUTPUT);
gpioSetMode(CONVST_AB, JET_OUTPUT);
gpioSetMode(RESET, JET_OUTPUT);
gpioWrite(CS_RD, 1);
gpioWrite(CONVST_AB, 1);
gpioWrite(RESET, 0);

ADC7606_Reset();

while (1) {
    // Measure how long it takes in nanoseconds
    clock_gettime(CLOCK_MONOTONIC, &start);

    for (int channel = 0; channel < NUM_CHANNELS; channel++) {
        // Start conversion
        gpioWrite(CONVST_AB, 0);
        gpioWrite(CONVST_AB, 1);

        while (gpioRead(BUSY)) {
            // Wait for conversion to complete
        }

        // Enable data output
        gpioWrite(CS_RD, 0);

        // Read all the data input pins
        Vx[channel] = 0;
        for (unsigned i = 8; i < 16; i++) {
            int pin_value = gpioRead(pin_number[i]);
            Vx[channel] |= (pin_value << (i - 8 + 8)); // Read the higher bits first
        }

        gpioWrite(CS_RD, 1);
    }

    clock_gettime(CLOCK_MONOTONIC, &end);
    diff = (end.tv_sec * BILLION + end.tv_nsec) - (start.tv_sec * BILLION + start.tv_nsec);
    elapsed_seconds = (double)diff / BILLION;

    Convert_Volt(Vx, voltages, NUM_CHANNELS, xferFactor);

    for (int channel = 0; channel < NUM_CHANNELS; channel++) {
        printf("Channel %d Raw ADC Value: %d\n", channel, Vx[channel]);
        printf("Channel %d Converted Voltage: %.5f V\n", channel, voltages[channel]);
    }

    printf("Elapsed time = %.9f seconds\n", elapsed_seconds);

    usleep(1000); // Optional: add a delay to reduce the read frequency
}

gpioTerminate();

return 0;

}

It is looking OK to me, the only thing I would make sure is:
-Set the AD7606 pin PAR/SER/BYTE SEL to GND
-Power the AD7606 from the +5 & GND on the Orin
-Also the pins OS0, OS1 & OS2 to GND just in case
It should work, it you see the stuff on the oscilloscope then it has to show up in the Orin.


high severity security vulnerability: http-proxy

Security alert: https://github.com/zooniverse/text-editor/network/alert/yarn.lock/http-proxy/open
Dependabot PR: https://github.com/zooniverse/text-editor/pull/201
Versions prior to 1.18.1 are vunerable to Denial of Service. http-proxy is a proxying library that supports websockets. More info on the npm page: https://www.npmjs.com/package/http-proxy

Closed with #201


TrainResult wrong parameters on docs

While checking the code against the docs I noticed that the docs mention 3 positional parameters on pl.TrainResult class, but the code signature has 4.
Also in the getting started tutorial instances this class with the first positional parameter without explaining what it uses for. This last inconsistency is key because I can't figure if the tutorial intends to track the training loss for early_stop_on param (based on docs) or minimize param (based on source code).
PD: Also there is a typo in the tutorial part I referenced last (https://pytorch-lightning.readthedocs.io/en/latest/new-project.html#wrap-loss-in-a-trainresult-evalresult)

it seems very similar to #3093, mind do the same as https://github.com/PyTorchLightning/pytorch-lightning/issues/3093#issuecomment-679880672 🦝


[FLINK-35858][Runtime/State] Namespace support for async state

What is the purpose of the change
This PR add namespace for async state, for partitioning the state for internal usage.
Brief change log

Add type parameter for internal state APIs.
code path for creating state with namespace.
Forst support

Verifying this change
Some related existing tests have been modified.
Does this pull request potentially affect one of the following parts:

Dependencies (does it add or upgrade a dependency): no
The public API, i.e., is any changed class annotated with @Public(Evolving): no
The serializers: no
The runtime per-record code paths (performance sensitive): yes
Anything that affects deployment or recovery: JobManager (and its components), Checkpointing, Kubernetes/Yarn, ZooKeeper: no
The S3 file system connector: no

Documentation

Does this pull request introduce a new feature? no
If yes, how is the feature documented? not applicable

Thanks for the review, merging...


Instead of dict pop accessing dict value directly.

Summary
Since version 2.2.5 the load_weights function raises a TypeError while passing the filepath value with explicitly accessing the filepath parameter.
model.load_weights(filepath=my_path)
This does not work because the filepath is popped out of the kwargs dictionary inside the extract_named_arg function at line 469.
When returning the load_function at line 492 the kwargs dictionary does not contain filepath anymore.
Related Issues
PR Overview

[n] This PR requires new unit tests [y/n] (make sure tests are included)
[n] This PR requires to update the documentation [y/n] (make sure the docs are up-to-date)
[y] This PR is backwards compatible [y/n]
[n] This PR changes the current API [y/n] (all API changes need to be approved by fchollet)

I am not sure why one test failed, since i only changed one line, that does not affect any performance or functionality.
The failure in the travis log looks like an internal error.


Save facts with signatures

Provide an endpoint for client to send envelopes with facts. Authorize those facts using the provided signatures in addition to any provided identity.

Completed in PR #83


Enable copy & paste in Electron app

At this moment, the basic copy&paste doesn't work.
https://pracucci.com/atom-electron-enable-copy-and-paste.html

Fixed: https://github.com/hackjutsu/GiGist/commit/d7b86a57033bdb90542959b22954017af8b9e3ec


Optional order notes field that can be enabled via settings

This PR adds a Notes field to the order, and provides a setting in the Cart and Checkout section that can be used to enable it. When enabled, it is displayed as "Order notes" field in the billing address section.
Having a generic Order notes field is useful to a number of our merchants. Not all of them use shipping(in which case they could use delivery instructions field), so having a generic order notes field that is filled prior to the shipping-method selection phase is a useful addition.

Implemented those fixes in a separate commit

Great, I'll review by the end of the week


move dynamic interpreter thunk generation OOP

    HeapDeleteArray(sizeInBytes, writeBuffer);

can you fix the memory leak here, I missed this in my change
or, maybe we can use stack memory instead? at this point the stack usage should be very low for OOP JIT and background JIT, right?
otherwise maybe we can use stack to repeatedly do the copying (like 1KB by 1KB)

Refers to: lib/Common/Memory/MemUtils.cpp:45 in 2863255. [](commit_id = 286325525afb3e3cfb548704b0f8de3e29d4e355, deletion_comment = False)

Looks good, otherwise.

:shipit:

@dotnet-bot test this please


[REQ] File nesting - make indentation less chaotic

I love the file nesting feature, but visually I think an improvement could be made for clarity.
When a file has nesting, it is indented further to allow space for an arrow. This means that its not visually indented the same as all the other non nested files.
Usually, I'm using this to nest a components CSS file with its JS file. If a component doesn't need a CSS file, I still end up creating an empty css file just to keep the indentation the same. Otherwise sometimes in long lists it can be visually difficult to tell if I'm still in the parent directory because the indentation is all over the place.
Proposal:
I think there's three options that could help improve this:

Change all indentation if file nesting is enabled to leave room for an arrow on all files no matter what.
Dynamically determine if a folder has nested files and if so, fix the indentation of the other files in that folder to match.
Sort nested files to the top (same behavior's as actual folders)

I'd personally pick option 2.
I know there's some limitations to modifications to the file explorer with extensions, but alternatively, could this be achieved with an extension?

Have you seen #148974? One of the observations there is that some File Icon Themes play better that others when nesting is being used.

I did not see that one, I didn't even think about the icon set affecting the position of it and I'm using seti. The minimal icon set does indeed fix the weird indentation.
Closing this issue as it is a duplicate of the #148974


gnat{6,9,10,11}: support building a cross-compiler

Motivation for this change
This is somewhat working: pkgsCross.aarch64-multiplatform.buildPackages.gnat will now compile. However to achieve this it seems we need to disable building the runtime libada (see 9b107a9). As a result the GNAT cross compiler is not very useful.
Next thing to investigate is building libada as a standalone derivation.
Things done

[ ] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
Built on platform(s)

[ ] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
21.11 Release Notes (or backporting 21.05 Relase notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[ ] Fits CONTRIBUTING.md.

Looks like a good progress, LGTM.


I'm trying to integrate this project with a frontend,

Describe the feature
I'm trying to integrate this project with a frontend, but I'm encountering version conflicts when using Umi. I attempted to integrate it with nodejs+koa2, but that also failed. I'm hoping to run this project as a standalone service to provide an API for the frontend, which will help avoid version conflicts. If you can help me get this project up and running as a standalone service, it would be very helpful. Thank you.

Hmmm, gpt-3-encoder definitely has problems.
I'm not sure the exact issue you're running into, but I'm looking to replace that dependency.
This may be helpful for you:
async function example() {
  // To use ESM in CommonJS, you can use a dynamic import
  const { ChatGPTAPI } = await import(https://github.com/transitive-bullshit/chatgpt-api)

  const api = new ChatGPTAPI({ apiKey: process.env.OPENAI_API_KEY })

  const res = await api.sendMessage('Hello World!')
  console.log(res.text)
}

#336 and #334 look related as they all have to do with compat issues with gpt-3-encoder.

Hey there,
I just tried to spin up my first Vue3/Quasar/ChatGPT project and hit this issue. Trying to include the ChatGPTAPI from your repo directly gives me a CORS error. I'm running currently on localhost:9000.
Any chance you can whitelist localhost?
Thanks!!

Try the new version https://github.com/transitive-bullshit/chatgpt-api/releases/tag/v4.6.0
It replaces the troublesome gpt-3-encoder with a better dependency.

Any chance you can whitelist localhost?

Any CORS issues are happening in your webapp and have nothing to do with this project.


Errors in terminal upon setting up for first time

ls: cannot access '/home/gitpod/.bashrc.d/*': No such file or directory
direnv: error /workspace/template-nix/.envrc is blocked. Run `direnv allow` to approve its content

How do I fix these?

Run direnv allow


test(e2e): update IO soak and basic volume IO tests

IO soak test:

monitor health of all MSVs
monitor online state of all pools

Basic volume IO test:
Add functionality for late binding of volumes,
ie WaitForFirstConsumer
for NVMe-of volumes the test matrix is now
- Filesystem volume with immediate binding
- Filesystem volume with delayed binding
- Raw block volume with immediate binding
- Raw block volume with delayed binding
iSCSI volume testing is unchanged
Make a few global var strings constants
Add function so that VolumeType vars are printed as
human readable strings.

bors merge


bump chart version

[ ] Chart version not bumped (the versions are all bumped and released at the same time)
[ ] README.md updated with any new values or changes
[ ] Updated template tests in ${CHART}/tests/*.py
[ ] Updated integration tests in ${CHART}/examples/*/test/goss.yaml

Since this is a community submitted pull request, a Jenkins build has not been kicked off automatically. Can an Elastic organization member please verify the contents of this patch and then kick off a build manually?

https://github.com/elastic/helm-charts/issues/177

I'm closing this one out until we have more troubleshooting information and can reproduce the issue you are having in #177. Changing the variable names is not going to be the solution as this is a breaking change.


Will beaker browser be available on smartphones?

I have been using beaker browser for a long time and have been loving it, but will it be available on Android/iOS?

Check out Gateway: https://twitter.com/GatewayBrowser


Mutex.under does not release lock upon crashes

Hi! First off, thanks for this excellent library.
Now if I load this module into IEx:
defmodule Mutest do
  def foo do
    Mutex.under(:some_mutex, :key, fn ->
      exit(:hello)
    end)
  end
end

And then call it:
iex(2)> Mutest.foo()
** (exit) :hello
    iex:4: anonymous fn/0 in Mutest.foo/0
    (mutex 1.1.3) lib/mut.ex:262: Mutex.apply_with_lock/3
iex(2)> Mutest.foo()

*IEx freezes*

This is a problem when a process crashes without properly throwing. We've seen this happen in practice (though not in mutexed code) when a database pool timed out and a calling process crashed because of it. I'm not a deep enough BEAM guru to understand exactly when something comes a :throw and when something is an :exit, but this was an :exit ☺
We found that Mutex had the same problem when we tried to use it to replace another library that froze upon crashing.
If this is indeed considered a bug and not by design, then it might be a matter as simple as adding an :exit clause to this catch, but not sure.
Also, my compliments on the mut.ex filename.

Hi,
For some reason I was not notified. I'll look into it.

Hi,
For some reason I was not notified. I'll look into it.

Hi again,
First, thanks for the kind words.
Regarding your problem, it is because there is a special behaviour in iex that prevents the process to actually exit.
If you modify your module to print the pid like that:
defmodule Mutest do
  def foo do
    Mutex.under(:some_mutex, :key, fn ->
      IO.puts "exiting from #{inspect self}"
      exit(:hello)
    end)
  end
end

You can run the same session:
iex(2)> Mutex.start(:some_mutex)
{:ok, #PID<0.251.0>}
iex(3)> self()
#PID<0.235.0>
iex(4)> Mutest.foo
exiting from #PID<0.235.0>
** (exit) :hello
    iex:5: anonymous fn/0 in Mutest.foo/0
    (mutex 1.2.0) lib/mut.ex:262: Mutex.apply_with_lock/3
iex(4)> self()
#PID<0.235.0>
iex(5)> Mutest.foo()
=> hangs

And you see that the two calls to self() returns the same pid. The process did not actually exit.
If you run the code in a "normal" process with spawn(fn -> Mutest.foo() end), it works as expected.
I added this test to show that the current implementation behaves well when exit/1 is called from the callback.
The mutex process monitors the processes that lock keys, so whenever they exit, their locks are released. This is why I do not catch exits, indeed, by design.
I wouldn't like to add an :exit clause to the catch as it should not be needed. Could you provide a simple example (or best, a failing test) of a lock not being released upon exit, that fails even when not called from iex ?

Hi again,
First, thanks for the kind words.
Regarding your problem, it is because there is a special behaviour in iex that prevents the process to actually exit.
If you modify your module to print the pid like that:
defmodule Mutest do
  def foo do
    Mutex.under(:some_mutex, :key, fn ->
      IO.puts "exiting from #{inspect self}"
      exit(:hello)
    end)
  end
end

You can run the same session:
iex(2)> Mutex.start(:some_mutex)
{:ok, #PID<0.251.0>}
iex(3)> self()
#PID<0.235.0>
iex(4)> Mutest.foo
exiting from #PID<0.235.0>
** (exit) :hello
    iex:5: anonymous fn/0 in Mutest.foo/0
    (mutex 1.2.0) lib/mut.ex:262: Mutex.apply_with_lock/3
iex(4)> self()
#PID<0.235.0>
iex(5)> Mutest.foo()
=> hangs

And you see that the two calls to self() returns the same pid. The process did not actually exit.
If you run the code in a "normal" process with spawn(fn -> Mutest.foo() end), it works as expected.
I added this test to show that the current implementation behaves well when exit/1 is called from the callback.
The mutex process monitors the processes that lock keys, so whenever they exit, their locks are released. This is why I do not catch exits, indeed, by design.
I wouldn't like to add an :exit clause to the catch as it should not be needed. Could you provide a simple example (or best, a failing test) of a lock not being released upon exit, that fails even when not called from iex ?

I thought about it and indeed, if you catch the exit outside of the callback then the problem arises, just as in iex. Is that what you do in your app?
I am not sure if mutex should handle this case. On one hand, it should because the under/4 function. On the other hand, exits are special. I will ask on the forums.

I thought about it and indeed, if you catch the exit outside of the callback then the problem arises, just as in iex. Is that what you do in your app?
I am not sure if mutex should handle this case. On one hand, it should because the under/4 function. On the other hand, exits are special. I will ask on the forums.

Well,
I just replaced the wrapper with that:
  defp apply_with_lock(mutex, lock, fun) do
    fun.(lock)
  after
    release(mutex, lock)
  end

So it works as intended, even with exits, and without the bookkeeping for rethrowing :)

Well,
I just replaced the wrapper with that:
  defp apply_with_lock(mutex, lock, fun) do
    fun.(lock)
  after
    release(mutex, lock)
  end

So it works as intended, even with exits, and without the bookkeeping for rethrowing :)


changing "libseat" to "seatd"

Description of changes
Changing "libseat" to "seatd"
Things done

changing "libseat" to "seatd" in includes and build

Built on platform(s)

[ ] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)

[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage

[ ] Tested basic functionality of all binary files (usually in ./result/bin/)

22.11 Release Notes (or backporting 22.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[ ] Fits CONTRIBUTING.md.

hi
Your commit message doesn't fit https://github.com/NixOS/nixpkgs/blob/master/CONTRIBUTING.md , it should be something like weston: rename libseat to seatd
and it was fixed 1h ago https://github.com/NixOS/nixpkgs/commit/d745231c7780ec5e3a336a7b03b7b7739d197ed9 :)

hi
Your commit message doesn't fit https://github.com/NixOS/nixpkgs/blob/master/CONTRIBUTING.md , it should be something like weston: rename libseat to seatd
and a fix was merged #194550

Ok,my bad didn't read contrib file, anyways good its fixed


[Question] Raspberry PI 2/3 install compatibility

Installation Issue

Description
I followed edge installation guide in Ubuntu.
https://thingsboard.io/docs/user-guide/install/edge/deb-installation/
When I install edge in Mac mini desktop which with Ubuntu 20, everything is clear.
But when I tried it with Raspberry PI 2 and Raspberry PI 3, the result is below.
Raspberry PI 2 with Ubuntu 20 32bit -> successfully install but some sort of important table in DB is empty. ex) edge, user, user-credentials table ... so I couldn't login to edge.
Raspberry PI 3 with Ubuntu 20 64bit -> successfully install but some sort of important table in DB is empty. ex) edge, user, user-credentials table ... so I couldn't login to edge.
Raspberry PI 3 with Ubuntu 22 64bit -> installation failed neither progress is slower than Ubuntu 20.

Environment
Edge

OS :  Ubuntu 20 32bit/64bit, Ubuntu 22 64bit (Raspberry PI 2, Raspberry PI 3)
CPU : ARMv7, ARMv8-A
RAM : 1GB
Edge : 3.5.1

Thingsboard

OS : Mac (M1)
ThingsBoard: 3.5.1

Question
I also viewed related topic, and it seems 3.4.3 would be solving these issue.
arm7 compatibility
And I also viewed someone successfully install edge in Raspberry PI 4.
Successfully Raspberry PI 4 install
Can I run edge in Raspberry PI 2/3 with low 1GB memory model? Or go to Raspberry PI 4?
Or is there any other suggestion about empty DB problem?
Best Regards, SeungChan

@Seungchan-Daliworks,
Hello, could you please attach the install.log and tb-edge.log files? Analyzing them will aid us in identifying the potential root cause of the issue. We plan to conduct some tests on PI 3, but we will first need to acquire the necessary equipment.

Sure,
tb-edge.log
install.log
Best Regards, SeungChan

@Seungchan-Daliworks,
I haven’t identified any errors in the logs provided. Could you please attach either the install or tb-edge logs that contain error messages, especially those related to the DB schema or any other issues? Additionally, please ensure that the logs are complete, starting from the application's startup.
Thank you in advance.

Oh, I've made some mistakes.
This log file has more information and error log.
tb-edge.log

@Seungchan-Daliworks,
It appears that the Edge is unable to establish a connection with the cloud, as indicated by the following error:
Caused by: io.grpc.netty.shaded.io.netty.channel.AbstractChannel$AnnotatedConnectException: Connection refused: /<IP_ADDRESS>:7070
Could you please verify whether port 7070 on IP address <IP_ADDRESS> is accessible from this Edge instance, using telnet or another network tool?
Additionally, could you provide the logs from your TB server instance? Are there any error messages present in those logs?

You're right I didn't write correct cloud IP address to .conf file.
After trying one more installation process, I do reply to you.
Thank you
Best Regards, SeungChan

@Seungchan-Daliworks,
If you have the opportunity, we recommend updating to the latest 3.6.0 version. We have expanded the Edge installation instructions, and Ubuntu OS is now supported as well. You can follow the steps in these updated instructions, which include all the prepared configuration parameters for your convenience:

@volodymyr-babak
It worked fine, finally edge is successfully installed and executed in Raspberry PI 2 and 3 with appropriate DB data.
Also, I want to share some trouble shooting case in Raspberry PI. If using Ubuntu in Raspberry PI 2 or 3, often I could see 'unattached upgrade' process spend almost 100% of CPU resource. Stuck resource seems affect installation process (jdk, postgresql and edge).

After change setting on 'unattached upgrade' process, I could install edge file normally as expected and faster. Referenced link is below.
Reference Link
So, it's remarkable to check whether 'unattached upgrade' process is active or not, before install edge in initialized Raspberry PI.
Thank you
Best Regards, SeungChan

@Seungchan-Daliworks,
Thank you for sharing this valuable information regarding the installation process of Edge for Raspberry Pi 2 or 3.
I believe this will be highly beneficial for other community members.


Separate different tasks as cogs

Everything is kind of polluting the main file, we should make it more modular with the use of cogs.

Lots of progress has been done and there's too many commits to address. It wasn't really worked through a branch, so you'll have to take my word on it.

PR #26 completes this, well done!


Couple of spelling errors?

HYPTHENS vs hyphens
"Sid": "AllowIndividualUserToManageThierMFA" -- misspelled THEIR?

Thanks, updated! :)


Custom status resetting

Sometimes, the bot's custom status resets, probably because Heroku restarts the bot. The only solution is to switch hosting platforms.

Will now be using Replit!


Unable to contribute to Notebook toolbar in VS Code stable

Not sure whether this is by design or not (by design as in, we're still reviewing whether this toolbar is to be made stable or not).
Extension authors contributing to Notebooks will be forced to contribute to the Editor toolbar
@roblourens @rebornix /cc

Good catch, we can now remove the proposed extension check.


Proposal: A more robust solution for truncating file names

Currently in this line, info_dict['title'] is truncated to 200 characters. This is first done by @phihag in 0599ef8c0827068184f78745a299d043927db4d9. This implementation can't handle wide characters correctly. An examples are #5740. I think YoutubeDL should switch to a utf-8 friendly implementation.
There's an implementation at a stackoverflow answer, although I haven't tested it. Any opinions?

As an addition: it still may not be enough since max filename limitation in general can be arbitrary (see #5908).

Another side note: on Windows file system encoding is not always utf-8, which make thinks more complicated. For example, on Traditional Chinese Windows file system uses big5 (cp950), where each Chinese character occupies 2 bytes rather than 3 bytes in utf-8.

This is still an issue, at least in Windows, and can be further exacerbated depending on the character length of the directory path that youtube-dl is outputting files in. --restrict-filenames doesn't trim it and there's no option to truncate the filename either still. A simple -truncate ## parameter would suffice just fine, or perhaps even an auto value that checks total file path length.

Also an issue in Linux, and moderator keeps closing new issues on this without referencing or addressing the original issue.

I've got the same error message, add here for reference and seaching
https://github.com/ytdl-org/youtube-dl/issues/23702


Fix footer links

Fix discord footer link and remove trailing slash from repo URL

Messages

:book:
:sparkles: Thanks for your contribution to Shields, @XhmikosR!

  Generated by :no_entry_sign: dangerJS against 7ce40413c4cf6f7eebe65a35557e0807fcd616da

Nice one, thanks!

@paulmelnikow: there's another issue but I don't know where the cause is.
C:\Users\XhmikosR\Desktop>curl -ILl https://shields.io/category/coverage
HTTP/2 301
server: GitHub.com
content-type: text/html
location: http://shields.io/category/coverage/
access-control-allow-origin: *
expires: Thu, 28 Feb 2019 17:03:47 GMT
cache-control: max-age=600
x-github-request-id: A6C0:7DE8:1FA40D:28C77D:5C78121B
accept-ranges: bytes
date: Thu, 28 Feb 2019 16:53:48 GMT
via: 1.1 varnish
age: 0
x-served-by: cache-lcy19243-LCY
x-cache: MISS
x-cache-hits: 0
x-timer: S1551372828.935303,VS0,VE78
vary: Accept-Encoding
x-fastly-request-id: 18cda7dd7a4e49ae4c6ca668e868c4b67b4dda12
content-length: 178

HTTP/1.1 301 Moved Permanently
Server: GitHub.com
Content-Type: text/html
Location: https://shields.io/category/coverage/
X-GitHub-Request-Id: 3884:6DFB:3557EF:44E926:5C78121C
Content-Length: 178
Accept-Ranges: bytes
Date: Thu, 28 Feb 2019 16:53:48 GMT
Via: 1.1 varnish
Age: 0
Connection: keep-alive
X-Served-By: cache-lcy19251-LCY
X-Cache: MISS
X-Cache-Hits: 0
X-Timer: S1551372828.158699,VS0,VE76
Vary: Accept-Encoding
X-Fastly-Request-ID: 0da254706096c015b87fb989bb2074601c43beb4

HTTP/2 200
server: GitHub.com
content-type: text/html; charset=utf-8
last-modified: Thu, 28 Feb 2019 00:11:22 GMT
etag: "5c77272a-9b87"
access-control-allow-origin: *
expires: Thu, 28 Feb 2019 17:03:48 GMT
cache-control: max-age=600
x-github-request-id: 8094:10BF:1D3DAB:25E798:5C78121C
accept-ranges: bytes
date: Thu, 28 Feb 2019 16:53:48 GMT
via: 1.1 varnish
age: 0
x-served-by: cache-lcy19243-LCY
x-cache: MISS
x-cache-hits: 0
x-timer: S1551372828.341464,VS0,VE75
vary: Accept-Encoding
x-fastly-request-id: 074f5f86ea3943959ada76becd15069da24c88d4
content-length: 39815

See the 3 redirects?


Form Templates for Defects & Enhancements

Already working on it ^^

Everything despite a Defect is an Enhancement or do we want to support more things?

Hmm. Open to discussion, but my initial thought is:

Defect (Behaviour is broken)
Enhancement (Add new feature)
Change (Change existing feature)
Operations (Infra & Automation)

I think I'll add some things and we can elaborate things on the PR


part 1 and improve ReadMe

Link to issue with details of Part 1 Additions

Link to issue with details of README Improvements


[NFC] Add bazel support to cpu_features

Fixes #221

tested with bazelisk-linux-amd64 test ...

Do we need to provide "Build with Bazel" documentation or will it be a separate patch?

@toor1245 good point ! Let's do it as a second step though, I suspect there will be a few iterations before everything works as correctly. We also need to setup continuous integration.


Can't use keyboard shortcuts to copy/paste/select-all on fallback-input-type="color"

Hi,
First of all thanks for this amazing library. I have recently integrated the advanced colour picker feature on my webpage and lot of users are reporting on being unable to use keyboard shortcuts to copy/paste/select-all on the input box in fallback-input mode.
This is the input I am talking about. It would be great if this can be addressed.

Hi,
pretty much the same as #56


feat: proper group actions

We define proper action of a group on a topological space, and we prove that in this case the quotient space is T2. We prove that if a Hausdorff group acts properly on $X$, then $X$ is Hausdorff. We also give equivalent definitions of proper action using ultrafilters and show the transfer of proper action to a closed subgroup.
We show that if $X \times X$ is Hausdorff and compactly generated then the action is properly discontinuous if and only if it is continuous in the second variable and proper in the sense defined here. The "compactly generated" assumption is to be rephrased with typeclass inference in the future.
Co-authored-by: @EtienneC30
Co-authored-by: @florestan
Co-authored-by: @ADedecker

[x] depends on: #11754
[x] depends on: #13635

@ADedecker I've created #11769 to see what happens removing the simp attribute that caused the linter failure. It seems tricky to really solve the problem.

(I'm assigning you, Anatole, since you definitely know the relevant mathematics, but if you think you have participated in this PR to much to review it, feel free to assign eg Floris instead)

The PR description says "Again compactly generated spaces are not yet in Mathlib". I think they now are, aren't there? CC @dagurtomas

The PR description says "Again compactly generated spaces are not yet in Mathlib". I think they now are, aren't there? CC @dagurtomas

Indeed I see they are. The property I need from compactly generated spaces is the direct implication in the following:
example {X : Type*} [TopologicalSpace X] [T2Space X] :
    CompactlyGeneratedSpace X ↔
      (∀ s, IsClosed s ↔ ∀ (K : Set X), IsCompact K → IsClosed (s ∩ K))

I managed to prove it. Now the interesting result in this PR is for locally compact spaces or T1 spaces, which are currently not deduced from compactly generated space by typeclass inference. The converse implication above would allow to prove the results without typeclass inference, but

it's probably better if everything is automatically inferred
I'm not even sure the converse direction is true. I have a proof in mind but I have trouble with universes, which I've never manipulated. Here's my attempt: #15066.

Note also that the current API on compactly generated spaces is very minimal, and should be expanded to prove theorems like the ones you mention.

Thanks, I've nailed it! I'll see what I can do for the instances.

Thanks!

Thanks!
bors merge


Add compatibility with Watersource mod

The trees from Watersource mod https://www.curseforge.com/minecraft/mc-mods/water-source
are not taken into account by Tree Chop, would be great to add this compatibility.

Thanks for reporting! Looks like it's an issue with WaterSource not giving coconut leaves the proper tag. If you turn off TreeChop's "Trees must have leaves" option, you'll be able to cut WaterSource's trees (their leaves aren't being recognized).

I find this option pretty clever, so when you cut the head of the tree, the rest isn't taken as a tree to cut in once.
It avoids also trees used as pilars to be cut in once.
Do you think it's possible to take into account their leaves ?
Maybe should we report this to water source mod ?
I've also noticed that baobab trees from byg aren't fully cut because some tree blocks have just a corner in common.
Do you think it's possible to add a check if the tree goes in diagonal corner up ?

Maybe should we report this to water source mod ?

I just reported this to WaterSource in https://github.com/lemon-slice-studio/WaterSource/issues/50

Do you think it's possible to add a check if the tree goes in diagonal corner up ?

Yeah, it's already checking for upward-diagonal blocks. I think the baobabs are either a) too big or b) have disconnected logs, or logs connected only by leaves. I've added baobabs to the list in #44, so I'll try to fix that eventually

So great !
Take you so much for your amazing work

The WaterSource folks say they've fixed it on their end, so I'm gonna close this. Thanks again for reporting!


Issue 459 - Use enums in place of strings

Do not merge
To Do

[x] Implement Functionality for Subcommands
[x] Add subcommands! macro
[x] Update Subcommands Docs
[x] Update Subcommands Examples
[ ] Add Subcommands Enum Examples
[ ] Implement  functionality for Args
[ ] Add args! macro
[ ] Update Args Docs
[ ] Update Args Examples
[ ] Add Args Enum Examples
[ ] Find any breaks in the wild
[ ] Warn of any breaks

Possible Breakages
Here's the list of possible breakages in the wild that I can find (crossed off as I warn/inform):

[ ] Keats/gutenberg
[ ] jadencarver/rusty-rails
[ ] matthiasbeyer/imag
[ ] pijul/pijul
[ ] jhelwig/homers

Those below clap v2 so shouldn't count against breakages

[ ] cmsd2/codelauf (1.4.0)
[ ] cwbriones/rgit (1.5.5)

Coverage decreased (-0.04%) to 88.681% when pulling 548036cd190b4bcb198021057953482b7cfb8c58 on issue-459 into 72ccf0cf6e9955d06d1d75fd88dc4137e07f0f68 on master.

Coverage decreased (-0.02%) to 88.704% when pulling 548036cd190b4bcb198021057953482b7cfb8c58 on issue-459 into 72ccf0cf6e9955d06d1d75fd88dc4137e07f0f68 on master.

You can consider jhelwig/homers informed/warned. :wink: I've been following the discussion around this pretty closely, and have been looking forward to trying it out. :+1:

@jhelwig great! This may change slightly as I work with different ideas to try and minimize the breaking changes and such. Once I'm reading to merge, I'll at-mention everyone and give some reasonable notice about how to fix before merging.

:umbrella: The latest upstream changes (presumably #482) made this pull request unmergeable. Please resolve the merge conflicts.

An update, I've come up with a way to combine this with a docopt style macro to get rid of nearly all the "stringly" typed-ness. I'm going to be working on this and add it to this PR as I work through some of the final bugs, but here's what it looks like so far:
#[macro_use]
extern crate clap;

use clap::{App, Arg};

args!{
    MyProg => MyProgArgs {
        name: String,
        age: u32
    }
}

fn main() {
    let args: MyProg = App::new("Test Struct App")
        .arg(Arg::with_name(MyProgArgs::name)
            .long("name")
            .value_name("NAME")
            .help"(some name"))
        .arg(Arg::with_name(MyProgArgs::age)
            .long("age")
            .short("a")
            .value_name("NUM")
            .help"(some age"))
        .get_matches()
        .into();

    println!("My name is {} and I'm {} years old", args.name.unwrap(), args.age.unwrap_or(2000));
}

Like, I said, there's still some kinks to workout so it'll be a bit before I get it all figured out...but just wanted to update.
Relates to #465

This pull request will be super-ceded by the v3.x branch merge once ready.


Updated a Campaign - got blank screen

I went onto the site as an administrator and changed an existing campaign's info (dates, address, contact info etc.) and clicked to save it. The screen went blank and the url became http://allready-d.azurewebsites.net/Account/AccessDenied.

Shweta M  looking at this.

Could not replicate the issue.


flutter run crashes: The application's Info.plist does not contain CFBundleVersion.

Steps to Reproduce

flutter create -t plugin --org mingsin.demo dmeo
cd dmeo/example
flutter run

Target Platform:
Target OS version/browser:
Devices:
Logs

command
flutter run
exception
ProcessException: ProcessException: Process "/usr/bin/xcrun" exited abnormally:
An error was encountered processing the command (domain=NSPOSIXErrorDomain, code=22):
Failed to install the requested application
The application's Info.plist does not contain CFBundleVersion.
Ensure your bundle contains a CFBundleVersion.
Command: /usr/bin/xcrun simctl install 5F000B3A-B2B9-487B-87FF-3CCB9FAF9B87 /Users/trevorwang/Dev/flutter/workspace/dmeo/example/build/ios/iphonesimulator/Runner.app
#0      runCheckedAsync (package:flutter_tools/src/base/process.dart:259:7)
<asynchronous suspension>
#1      SimControl.install (package:flutter_tools/src/ios/simulators.dart:145:16)
#2      IOSSimulator._setupUpdatedApplicationBundle (package:flutter_tools/src/ios/simulators.dart:437:31)
<asynchronous suspension>
#3      IOSSimulator.startApp (package:flutter_tools/src/ios/simulators.dart:339:15)
<asynchronous suspension>
#4      FlutterDevice.runHot (package:flutter_tools/src/resident_runner.dart:378:54)
#5      _asyncThenWrapperHelper.<anonymous closure> (dart:async-patch/async_patch.dart:71:64)
#6      _rootRunUnary (dart:async/zone.dart:1132:38)
#7      _CustomZone.runUnary (dart:async/zone.dart:1029:19)
#8      _FutureListener.handleValue (dart:async/future_impl.dart:137:18)
#9      Future._propagateToListeners.handleValueCallback (dart:async/future_impl.dart:678:45)
#10     Future._propagateToListeners (dart:async/future_impl.dart:707:32)
#11     Future._completeWithValue (dart:async/future_impl.dart:522:5)
#12     Future._asyncComplete.<anonymous closure> (dart:async/future_impl.dart:552:7)
#13     _rootRun (dart:async/zone.dart:1124:13)
#14     _CustomZone.run (dart:async/zone.dart:1021:19)
#15     _CustomZone.runGuarded (dart:async/zone.dart:923:7)
#16     _CustomZone.bindCallbackGuarded.<anonymous closure> (dart:async/zone.dart:963:23)
#17     _microtaskLoop (dart:async/schedule_microtask.dart:41:21)
#18     _startMicrotaskLoop (dart:async/schedule_microtask.dart:50:5)
#19     _runPendingImmediateCallback (dart:isolate-patch/isolate_patch.dart:116:13)
#20     _RawReceivePortImpl._handleMessage (dart:isolate-patch/isolate_patch.dart:173:5)

flutter doctor
[✓] Flutter (Channel stable, v1.9.1+hotfix.4, on Mac OS X 10.15 19A583, locale en-CN)
    • Flutter version 1.9.1+hotfix.4 at /Users/trevorwang/Dev/flutter/sdk
    • Framework revision cc949a8e8b (12 days ago), 2019-09-27 15:04:59 -0700
    • Engine revision b863200c37
    • Dart version 2.5.0

[✓] Android toolchain - develop for Android devices (Android SDK version 29.0.2)
    • Android SDK at /Users/trevorwang/Dev/Android/sdk
    • Android NDK location not configured (optional; useful for native profiling support)
    • Platform android-29, build-tools 29.0.2
    • ANDROID_HOME = /Users/trevorwang/Dev/Android/sdk
    • Java binary at: /Applications/Android Studio.app/Contents/jre/jdk/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build 1.8.0_202-release-1483-b49-5587405)
    • All Android licenses accepted.

[✓] Xcode - develop for iOS and macOS (Xcode 11.1)
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • Xcode 11.1, Build version 11A1027
    • CocoaPods version 1.7.5

[!] Android Studio (version 3.5)
    • Android Studio at /Applications/Android Studio.app/Contents
    ✗ Flutter plugin not installed; this adds Flutter specific functionality.
    ✗ Dart plugin not installed; this adds Dart specific functionality.
    • Java version OpenJDK Runtime Environment (build 1.8.0_202-release-1483-b49-5587405)

[✓] VS Code (version 1.39.0)
    • VS Code at /Applications/Visual Studio Code.app/Contents
    • Flutter extension version 3.5.1

[✓] Connected device (1 available)
    • iPhone 11 Pro Max • 5F000B3A-B2B9-487B-87FF-3CCB9FAF9B87 • ios • com.apple.CoreSimulator.SimRuntime.iOS-13-1 (simulator)

! Doctor found issues in 1 category.

I get the same problem.

I am seeing the same behavior.
$ flutter doctor -v

[✓] Flutter (Channel stable, v1.9.1+hotfix.5, on Mac OS X 10.15 19A602, locale en-US)
    • Flutter version 1.9.1+hotfix.5 at /Users/me/source/flutter
    • Framework revision 1aedbb1835 (26 hours ago), 2019-10-17 08:37:27 -0700
    • Engine revision b863200c37
    • Dart version 2.5.0

[✓] Android toolchain - develop for Android devices (Android SDK version 28.0.3)
    • Android SDK at /Users/me/Library/Android/sdk
    • Android NDK location not configured (optional; useful for native profiling support)
    • Platform android-28, build-tools 28.0.3
    • Java binary at: /Applications/Android Studio.app/Contents/jre/jdk/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build 1.8.0_202-release-1483-b49-5587405)
    • All Android licenses accepted.

[✓] Xcode - develop for iOS and macOS (Xcode 11.1)
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • Xcode 11.1, Build version 11A1027
    • CocoaPods version 1.8.4

[✓] Android Studio (version 3.5)
    • Android Studio at /Applications/Android Studio.app/Contents
    • Flutter plugin version 40.2.2
    • Dart plugin version 191.8423
    • Java version OpenJDK Runtime Environment (build 1.8.0_202-release-1483-b49-5587405)

[✓] VS Code (version 1.39.2)
    • VS Code at /Applications/Visual Studio Code.app/Contents
    • Flutter extension version 3.5.1

[✓] Connected device (1 available)
    • iPhone 11 • 329CCB49-5B03-48C8-8873-AEB59AE71172 • ios • com.apple.CoreSimulator.SimRuntime.iOS-13-1
      (simulator)

• No issues found!

Closing, this was fixed with https://github.com/flutter/flutter/pull/40611 which first appeared in 1.10.4.
Duplicate of https://github.com/flutter/flutter/issues/34477.


[Flakey CI] [rfe_id:150][crit:high][vendor:cnv-qe@redhat.com][level:component]Networkpolicy when three cirros VMs with default networking are started and serverVMI start an HTTP server on port 80 and 81 and connectivity between VMI/s is blocked by Default-deny networkpolicy [test_id:1511] should fail to reach serverVMI from clientVMI

Is this a BUG REPORT or FEATURE REQUEST?:

Uncomment only one, leave it on its own line:

/kind bug
/triage build-officer
What happened:
Flakefinder found this test to be flakey:
[rfe_id:150][crit:high][vendor:cnv-qe@redhat.com][level:component]Networkpolicy when three cirros VMs with default networking are started and serverVMI start an HTTP server on port 80 and 81 and connectivity between VMI/s is blocked by Default-deny networkpolicy [test_id:1511] should fail to reach serverVMI from clientVMI

Failed in this prowjob due to invalid interface conversion: Panic: interface conversion: runtime.Object is *v1.Status, not *v1.Event
https://prow.apps.ovirt.org/view/gcs/kubevirt-prow/pr-logs/pull/kubevirt_kubevirt/4196/pull-kubevirt-e2e-k8s-1.19/1308109881026285568
How to reproduce it (as minimally and precisely as possible):
Anything else we need to know?:
Environment:

KubeVirt version (use virtctl version):
Kubernetes version (use kubectl version):
VM or VMI specifications:
Cloud provider or hardware configuration:
OS (e.g. from /etc/os-release):
Kernel (e.g. uname -a):
Install tools:
Others:

/assign @qinqon

I see that at kubevirt we have client-go 0.16.4 but k8s is 1.19 could this be the issue ? openned at bug/question at k8s client-go https://github.com/kubernetes/client-go/issues/869

/reopen
#4246 only helps to debug this problem.


Unable to import on Mac OS X 10.10

Hi
This library looks pretty neat, but when i installed it and tried to import it on OS X i received the following import error:
Python 3.4.3 (default, Jul 13 2015, 12:18:23)
[GCC 4.2.1 Compatible Apple LLVM 6.1.0 (clang-602.0.53)] on darwin
Type "help", "copyright", "credits" or "license" for more information.
>>> import pyldap
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
  File "/Users/kradalby/git/garru/env/lib/python3.4/site-packages/pyldap/__init__.py", line 3, in <module>
    from pyldap.ldapconnection import LDAPConnection
  File "/Users/kradalby/git/garru/env/lib/python3.4/site-packages/pyldap/ldapconnection.py", line 1, in <module>
    from pyldap._cpyldap import _LDAPConnection
ImportError: dlopen(/Users/kradalby/git/garru/env/lib/python3.4/site-packages/pyldap/_cpyldap.so, 2): Symbol not found: _ldap_control_find
  Referenced from: /Users/kradalby/git/garru/env/lib/python3.4/site-packages/pyldap/_cpyldap.so
  Expected in: flat namespace
 in /Users/kradalby/git/garru/env/lib/python3.4/site-packages/pyldap/_cpyldap.so

I guess it may be a compile error?
OS X version is 10.10.4
Python 3.4.3
I have not installed any additional LDAP libs, or anything, this may be the problem?
Install command:
pip install git+https://github.com/Noirello/PyLDAP.git

I will be happy to provide any additional information if needed.

Well, the openldap (and sasl2) headers are needed for compiling, but I guess you would have noticed in error messages if they were missing after ran pip.
I did some research, and it seems that the pre-compiled OpenLDAP library on OS X somehow doesn't have an ldap_control_find, but only the deprecated ldap_find_control function. It's weird.
For temporally solution I can add this function manually, if the platform is OS X, but for testing I would like to ask for your help, because I don't have an available OS X system.

I have limited C/C++ knowledge, but i have noe problem with trying to use the packages and provide you with the result/output.
I pulled down the dev branch now, and when trying to compile, i received the following error:
$ python setup.py install
running install
running bdist_egg
running egg_info
creating pyldap.egg-info
writing top-level names to pyldap.egg-info/top_level.txt
writing dependency_links to pyldap.egg-info/dependency_links.txt
writing pyldap.egg-info/PKG-INFO
writing manifest file 'pyldap.egg-info/SOURCES.txt'
reading manifest file 'pyldap.egg-info/SOURCES.txt'
reading manifest template 'MANIFEST.in'
warning: no files found matching '*.c' under directory 'tests'
warning: no files found matching '*.h' under directory 'tests'
warning: no files found matching '*.css' under directory 'docs'
writing manifest file 'pyldap.egg-info/SOURCES.txt'
installing library code to build/bdist.macosx-10.10-x86_64/egg
running install_lib
running build_py
creating build
creating build/lib.macosx-10.10-x86_64-3.4
creating build/lib.macosx-10.10-x86_64-3.4/pyldap
copying pyldap/__init__.py -> build/lib.macosx-10.10-x86_64-3.4/pyldap
copying pyldap/errors.py -> build/lib.macosx-10.10-x86_64-3.4/pyldap
copying pyldap/ldapclient.py -> build/lib.macosx-10.10-x86_64-3.4/pyldap
copying pyldap/ldapconnection.py -> build/lib.macosx-10.10-x86_64-3.4/pyldap
copying pyldap/ldapdn.py -> build/lib.macosx-10.10-x86_64-3.4/pyldap
copying pyldap/ldapentry.py -> build/lib.macosx-10.10-x86_64-3.4/pyldap
copying pyldap/ldapurl.py -> build/lib.macosx-10.10-x86_64-3.4/pyldap
running build_ext
building 'pyldap._cpyldap' extension
creating build/temp.macosx-10.10-x86_64-3.4
creating build/temp.macosx-10.10-x86_64-3.4/pyldap
clang -Wno-unused-result -fno-common -dynamic -DNDEBUG -g -fwrapv -O3 -Wall -Wstrict-prototypes -I/usr/local/Cellar/python3/3.4.3_2/Frameworks/Python.framework/Versions/3.4/include/python3.4m -c pyldap/pyldapmodule.c -o build/temp.macosx-10.10-x86_64-3.4/pyldap/pyldapmodule.o
In file included from pyldap/pyldapmodule.c:3:
In file included from pyldap/ldapconnection.h:7:
pyldap/ldap-xplat.h:14:1: error: unknown type name 'LDAPControl'
LDAPControl *ldap_control_find(const char *oid, LDAPControl **ctrls, LDAPControl ***nextctrlp);
^
pyldap/ldap-xplat.h:14:49: error: unknown type name 'LDAPControl'
LDAPControl *ldap_control_find(const char *oid, LDAPControl **ctrls, LDAPControl ***nextctrlp);
                                                ^
pyldap/ldap-xplat.h:14:70: error: unknown type name 'LDAPControl'
LDAPControl *ldap_control_find(const char *oid, LDAPControl **ctrls, LDAPControl ***nextctrlp);
                                                                     ^
3 errors generated.
error: command 'clang' failed with exit status 1

Thank you, I really appreciate your help.
I made a clumsy mistake and put the declaration before the includes.
I fixed and committed into the de branch.

Hello,
I tried to build the module from the dev branch, but there are still some errors:
Python 3.4.3 (default, Jul 13 2015, 12:18:23)
[GCC 4.2.1 Compatible Apple LLVM 6.1.0 (clang-602.0.53)] on darwin
Type "help", "copyright", "credits" or "license" for more information.
>>> import pyldap
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
  File "/Users/max/work/PyLDAP/venv/lib/python3.4/site-packages/pyldap-0.7.5-py3.4-macosx-10.10-x86_64.egg/pyldap/__init__.py", line 3, in <module>
    from pyldap.ldapconnection import LDAPConnection
  File "/Users/max/work/PyLDAP/venv/lib/python3.4/site-packages/pyldap-0.7.5-py3.4-macosx-10.10-x86_64.egg/pyldap/ldapconnection.py", line 1, in <module>
    from pyldap._cpyldap import _LDAPConnection
ImportError: dlopen(/Users/max/work/PyLDAP/venv/lib/python3.4/site-packages/pyldap-0.7.5-py3.4-macosx-10.10-x86_64.egg/pyldap/_cpyldap.so, 2): Symbol not found: _ldap_sasl_interactive_bind

After a while I found this page (http://projects.skurfer.com/posts/2011/python_ldap_lion/) and it describes that the OSX uses really old LDAP libraries, which does not have the missing _ldap_sasl_interactive_bind function
I checked and it's still just 2.4.0 in OS X 10.10.4:
% otool -L /usr/lib/libldap_r.dylib
/usr/lib/libldap_r.dylib:
    /System/Library/Frameworks/LDAP.framework/Versions/A/LDAP (compatibility version 1.0.0, current version 2.4.0)
    /usr/lib/libsasl2.2.dylib (compatibility version 3.0.0, current version 3.15.0)
    /System/Library/Frameworks/Security.framework/Versions/A/Security (compatibility version 1.0.0, current version 57031.20.16)
    /System/Library/PrivateFrameworks/CoreDaemon.framework/Versions/B/CoreDaemon (compatibility version 3.0.0, current version 3.0.0)
    /usr/lib/libresolv.9.dylib (compatibility version 1.0.0, current version 1.0.0)
    /System/Library/Frameworks/CoreFoundation.framework/Versions/A/CoreFoundation (compatibility version 150.0.0, current version 1153.15.0)
    /System/Library/Frameworks/SystemConfiguration.framework/Versions/A/SystemConfiguration (compatibility version 1.0.0, current version 699.1.5)
    /System/Library/Frameworks/IOKit.framework/Versions/A/IOKit (compatibility version 1.0.0, current version 275.0.0)
    /usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current version 1213.0.0)

There is a workaround also on the page (I didn't try it), but you can patch'n'hack new OpenLDAP libraries into the OS X and build the module against them.

yeah, i just found that page too.
I think that for me personally, i will just develop in a VM, since i am going to deploy on Linux anyways.
If i can help with any more OS X testing, just ask. But i dont think i can help with any of the C stuff :/

Testers are always more than welcome. :)
I've looked into it, and it seems at least version 2.4.24 is needed for the module (release date is around 2011). I'm going to check that hack for OS X somehow, and if I succeed, I will update the documentation about Mac OS X install. But it will take time, so probably good idea to use Linux for now.

The new  OS X release is around the corner, one can hope that they may up the version a little :P

Well, it took me awhile (sorry about the delay), but recently I managed to run a Mac OS X (10.11) in VirtualBox, and tested out the hack linked earlier. It works for me.
Updated the docs based on the blog post about Mac OS X install.
Also, thanks to this module, I will be able to create Mac OS X wheels for the next release, that will include the newer OpenLDAP libraries, so it will be not necessary to install them manually.


feat: support custom&in-cluster config

What type of this PR
Add one of the following kinds:
/kind feature
What this PR does / why we need it:

support use custom token&ca to create client config
supprot in-cluster to create client config

Which issue(s) this PR fixes:
Fixes #
Specified Reivewers:
/assign @your-reviewer

/approve


Android program

Can I run code from android program, like https://play.google.com/store/apps/details?id=com.paprbit.dcoder ?

Sure, I think it works quite well in Google Chrome. https://play.google.com/store/apps/details?id=com.android.chrome

You can add it to your home screen as a web app.