rename ent_reg_cost in sinkhorn solver

in sinkhorn.py, ent_reg_cost is used for a property of SinkhornOutput (see e.g. #376) but also as a method of the solver. This PR disambiguates both (and renames properly the method in the solver)

Codecov Report

Merging #391 (c8c1856) into main (172ba77) will decrease coverage by 0.09%.
The diff coverage is 80.00%.

:exclamation: Your organization is not using the GitHub App Integration. As a result you may experience degraded service beginning May 15th. Please install the Github App Integration for your organization. Read more.
Additional details and impacted files

@@            Coverage Diff             @@
##             main     #391      +/-   ##
==========================================
- Coverage   88.93%   88.85%   -0.09%
==========================================
  Files          55       55
  Lines        5929     5929
  Branches      861      594     -267
==========================================
- Hits         5273     5268       -5
- Misses        535      541       +6
+ Partials      121      120       -1

Impacted Files
Coverage Δ

src/ott/solvers/linear/sinkhorn.py
97.53% <75.00%> (ø)

src/ott/initializers/nn/initializers.py
91.35% <100.00%> (ø)

... and 1 file with indirect coverage changes


Update Stargate-builder image to use DSE 6.8.25

What this PR does:
Follow up to #2022 needed to make CI use DSE 6.8.25 as well.
Which issue(s) this PR fixes:
Checklist

[x] Changes manually tested
[ ] Automated Tests added/updated
[ ] Documentation added/updated
[x] CLA Signed: DataStax CLA

Doesn't the Dockerfile need to change as well?
https://github.com/stargate/stargate/blob/master/ci/Dockerfile#L57

Yes, but that was done in the first PR when updating references, so it already has 6.8.25.
As Ivan suggested in future it'd make sense to combine both PRs into just one.


fuzzy_scaffold can now return a pandas dataframe that is more readable.

Hello!  This is for issue #114.  So this edit is quite opinionated. I don't know if you guys would this kind of organized dataframe. But first I have to discuss where I added this change. I decided to add a optional flag for datamol users in the fuzzy_scaffolding function. The flag is termed if_df, which is defaulted to False.  The flag is termed if_df, which is defaulted to True.  Two separate pandas dataframe for each scf2infos and scf2groups will be returned. The rationale is not to confuse users on how fuzzy_scaffolding function would return previously.
NOTE: the output below is my best attempt to express the pandas dataframe. The output is just a df that has 3 columns and not 15 rows.
Let's start with scf2infos
The way scf2infos is structured is absolutely perfect to be pandas transposed. Every scaffold output has its corresponding rdkit mol list and its smarts pattern. This means every row will represent the scf and every scf will have its mol list.
output:
                                         scf  \
index
0                      CC(CC1CCCCC1)CC1CCCC1
1                     CC(CCC1CCCCC1)CC1CCCC1
2                    CC(CCCC1CCCC1)CCC1CCCC1
3                      CC(CC1CCCCC1)C1CCCCC1
4      CC(CCC1CCC(C2CCC3CCCCC32)C1)CC1CCCCC1

                                                    mols  \
index
0        [<rdkit.Chem.rdchem.Mol object at 0x1108a1a80>]
1      [<rdkit.Chem.rdchem.Mol object at 0x1108a06d0>...
2        [<rdkit.Chem.rdchem.Mol object at 0x1108a0200>]
3        [<rdkit.Chem.rdchem.Mol object at 0x1108a2dc0>]
4        [<rdkit.Chem.rdchem.Mol object at 0x1108a2c00>]

                                                  smarts
index
0      [#6]1:&@[#6]:&@[#6]:&@[#6](:&@[#6]:&@[#6]:&@1)...
1      [#6]-&!@[#8]-&!@[#6]1:&@[#6]:&@[#6]:&<EMAIL_ADDRESS>
2      [#6](-&!@[#7]-&!@[#6](=&!@[#8])-&<EMAIL_ADDRESS>
3      [#6]1-&@[#6]-&@[#6]-&@[#6]-&@[#6]-&<EMAIL_ADDRESS>
4      [#15](=,-;!@[#8,#7])(-&!@[#8]-&<EMAIL_ADDRESS>

What about scf2groups?
scf2groups is trickier because the core 'groups' are in their individual dictionaries contained in a list. This can be difficult to create a df due to these multi-valued attributes. Thankfully, Pandas can control for the multi-valued attributes by calling from the .from_dict() method and setting orient to 'index'. Further, this allows the df for each scf row to have None values if there are no results. So this df will dynamically create n_core_groups if there is an output with n number of core groups. So in the case below, scf index 1 has two core groups but the rest do not.
                                         scf  \
index
0                      CC(CC1CCCCC1)CC1CCCC1
1                     CC(CCC1CCCCC1)CC1CCCC1
2                    CC(CCCC1CCCC1)CCC1CCCC1
3                      CC(CC1CCCCC1)C1CCCCC1
4      CC(CCC1CCC(C2CCC3CCCCC32)C1)CC1CCCCC1

                                            0_core_group  \
index
0      {'Core': <rdkit.Chem.rdchem.Mol object at 0x11...
1      {'Core': <rdkit.Chem.rdchem.Mol object at 0x11...
2      {'Core': <rdkit.Chem.rdchem.Mol object at 0x11...
3      {'Core': <rdkit.Chem.rdchem.Mol object at 0x11...
4      {'Core': <rdkit.Chem.rdchem.Mol object at 0x11...

                                            1_core_group
index
0                                                   None
1      {'Core': <rdkit.Chem.rdchem.Mol object at 0x11...
2                                                   None
3                                                   None
4                                                   None

Other than that. I hope you like the code. I also updated the test cases.
Thanks,
Steven Pak
Checklist:

[x] Was this PR discussed in a issue? It is recommended to first discuss a new feature into a GitHub issue before opening a PR.
[x] Add tests to cover the fixed bug(s) or the new introduced feature(s) (if appropriate).
[ ] Update the API documentation is a new function is added or an existing one is deleted.
[x] Added a news entry.

copy news/TEMPLATE.rst to news/my-feature-or-branch.rst) and edit it.

It seems like I am having trouble dealing with conditional return typing for fuzzy_scaffolding . I am currently trying to figure out how to do this. I found a overload functionality for my issue, so I am gonna try that. IF you guys have any recommendations. That would be great.

It seems like I am having trouble dealing with conditional return typing for fuzzy_scaffolding . I am currently trying to figure out how to do this. I found a overload functionality for my issue, so I am gonna try that. IF you guys have any recommendations. That would be great.

@Pakman450, it's fine to break compatibility and return only the new structure here. This code has not been maintained for a while, and we should likely refactor most of it.  See here too: https://github.com/datamol-io/datamol/issues/119

It seems like I am having trouble dealing with conditional return typing for fuzzy_scaffolding . I am currently trying to figure out how to do this. I found a overload functionality for my issue, so I am gonna try that. IF you guys have any recommendations. That would be great.

@Pakman450, it's fine to break compatibility and return only the new structure here. This code has not been maintained for a while, and we should likely refactor most of it. See here too: #119

I changed the if_df defaulted to true, so it will always bring dataframes. Should I completely remove that flag and change to return type just to bring dataframes and no dictionaries?

@Pakman450 could you rebase this PR to main please as well? So we can make sure this PR is compatible with the latest rdkit.

Let's put the refactoring of the function itself in a different PR.
@Pakman450 can you document the column name in the dataframes ?
ping @hadim for planning refactoring later.

@maclandrol Where do you want me to document them? In the comments?

@Pakman450 could you rebase this PR to main please as well? So we can make sure this PR is compatible with the latest rdkit.

Sure. I give me a moment.

LGTM, thanks @Pakman450


Make tests stop build on error

Update script to make the automatic tests catch when testfiles should be updated.
(It just happend again.)

I like this change, but i want to add normalized output into test before merging this.

I'm not sure what normalized outputs means.
I would like this to be merged ASAP so noone can issue a pull request and forgot to update tests.
If you modify the output, you will have to touch all "golden files".

I'm not sure what normalized outputs means.

mbus_parse_hex supports a option -n. This supports parsing the M-Bus frame the new (normalized value) way found in mbus-protocol-aux. The normalized output is better for machine processing, while the default output (mbus-protocol) is more intended for humans.

I would like this to be merged ASAP so noone can issue a pull request and forgot to update tests.

I understand but your check would only handle half of the truth.

If you modify the output, you will have to touch all "golden files".

No, we need to add all the normalized output files.

Here as an example for allmess_cf50.hex
default output:
    <DataRecord id="4">
        <Function>Instantaneous value</Function>
        <StorageNumber>0</StorageNumber>
        <Unit>Flow temperature (1e-1 deg C)</Unit>
        <Value>1288</Value>
    </DataRecord>

normalized output:
    <DataRecord id="4">
        <Function>Instantaneous value</Function>
        <StorageNumber>0</StorageNumber>
        <Unit>°C</Unit>
        <Quantity>Flow temperature</Quantity>
        <Value>128.800000</Value>
    </DataRecord>

The necessary changes for generate-xml.sh is available in #168

Updated/rebased onto rscada/generate-norm-xml. Found one or two things that have bothered me. Please review!

Pushed a new version

@lategoodbye  : Can you review this PR please?

@lategoodbye , could you have another look?

@lategoodbye : New version, where I no longer check the count of errors, and instead accept that the two other directories does not exit with code zero.

Thanks


fix(masthead): set platform name z-index and background color

Related Ticket(s)
Masthead with Platform - Divider activates hover state on platform #5484
Description
There was work (PR: fix(Masthead): remove pseudo element from platform name #5835) to address the ticket by removing the pseudo element from the platform name, but in web components that led to the overflow menu options to show behind the platform name.
This PR addresses the overflow menu items by setting the z-index and background of the platform name.
BEFORE:

AFTER:

Changelog
Changed

set the z-index and background of top-nav-name component

looks good for web components but react is still showing :/

looks good for web components but react is still showing :/

Ah, I thought React was fine but I see it now at a specific breakpoint


Downloading maps on Windows is broken

Two people on Windows have reported this. Nothing in `output.txt` that looked unusual.
I just tried through wine and got:
[2021-12-23T09:21:32Z INFO  abstio::download] Downloading http://play.abstreet.org/dev/data/system/us/seattle/maps/arboretum.bin.gz
thread 'tokio-runtime-worker' panicked at 'called `Result::unwrap()` on an `Err` value: reqwest::Error { kind: Request, url: Url { scheme: "http", cannot_be_a_base: false, username: "", password: None, host: Some(Domain("play.abstreet.org")), port: None, path: "/dev/data/system/us/seattle/maps/arboretum.bin.gz", query: None, fragment: None }, source: hyper::Error(Connect, ConnectError("tcp connect error", Os { code: 10051, kind: NetworkUnreachable, message: "OS Error 10051 (FormatMessageW() returned error 317)" })) }', D:\a\abstreet\abstreet\abstio\src\download.rs:25:33

which may be a different problem. But why was it downloading from dev and not 0.3.4? The binary map format could've changed, so that could explain the timer error. Somehow the release_s3 feature isn't being picked up for the Windows build? https://github.com/a-b-street/abstreet/blob/44736a7937494c6c89104b3d9acbb106f6618037/map_gui/src/tools/mod.rs#L51

https://github.com/a-b-street/abstreet/blob/44736a7937494c6c89104b3d9acbb106f6618037/.github/workflows/main.yml#L37
This probably doesn't work on the Windows github runner :(

But did the shell evaluation actually happen? https://docs.github.com/en/actions/learn-github-actions/workflow-commands-for-github-actions#example-6 suggests it should happen differently


Add skeleton of wgpu-py

Starting from the top of #1
This PR starts with a squashed clone of wgpu-py at the 0.13.2 release and then removes all parts that are not required.
all inits and config are kept
no modifications to any files have been made

Is there anything else that needs to go?
will there be any issues by keeping the config files as is?

I will have a lot of feedback at this stage. I will post code review comments, but if you refer me to just add commits to the branch directly, tell me and I will.

It would be a ton of effort for me to capture my feedback in more comments so I just pushed some commits to this branch. Feel free to revert anything if you feel differently.
I used these two guides to put pyproject.toml together:

https://packaging.python.org/en/latest/guides/writing-pyproject-toml/#license
https://setuptools.pypa.io/en/latest/userguide/pyproject_config.html#dynamic-metadata

With CI passing and at least one example under screenshot testing, I think this is ready to merge.

Thanks for all the changes. I was reading through nearly the same resources yesterday.
The only issue I see with calling it just shadertoy is that it might be protected and we are clearly not affiliated with the website. So perhaps something like wgpu-shadertoy would work instead.
As for linting, I welcome new capabilities. Something that could be interesting, is that shadercode is just python strings - and could maybe get it's own linting rules (for glsl or wgsl specific).
It looks good to merge to me!

The only issue I see with calling it just shadertoy is that it might be protected and we are clearly not affiliated with the website. So perhaps something like wgpu-shadertoy would work instead.

That makes sense. We can rename the package to wgpu_shadertoy?

As for linting, I welcome new capabilities. Something that could be interesting, is that shadercode is just python strings - and could maybe get it's own linting rules (for glsl or wgsl specific).

Easiest way to accomplish that is probably to put shaders in their own .glsl and .wgsl files.


Inquiry about the environment of Diff-Foley

This project is fantastic! We found that Pytorch-lightning 1.8.6 with torch 2.1.0 does not work. Could you please inform me of the intended release date for its environment or the specific version of torch, pytorch-lighting? Thank you.

torch==2.2.0+cu121 and pytorch-lightning==1.2.0 work in my environment.

torch==2.2.0+cu121 and pytorch-lightning==1.2.0 work

Hey Yoonjin, thanks for your reply. The author has already released the environment then I have revised the code accordingly to be compatible with torch 2.1.0 + cu121 + pytorch-lighting=1.8.6. Thanks!

torch==2.2.0+cu121 and pytorch-lightning==1.2.0 work

Can you train it?Thanks!


When conda-store fails to connect to s3 it keeps the build in the BUILDING state instead of failed

@costrouc is this still valid? Is it backend or front end?


[1pt] Technical Setup and Project Layout [Group Task]

Setting up the project on GitHub, using git flow
Deciding on initializing the project as two separate apps or as one.
Creating the README and giving credit to the design author.

Done!


Use default credential provider chain

Allow for using the DefaultAWSCredentialProviderChain in place of requiring hardcoded access keys in the flume config.  This will allow using EC2 Instance Profiles and other methods to access Kinesis so users can avoid putting sensitive keys in plain text.
The existing hardcoded credentials are still supported for now to allow for backward compatibility.  If those are present in the config they take precedence over the default chain.

This is great... Have always want to get rid of aws keys 🎉

👍 👍 👍


Failed builds not pushing artifacts on quit

See original issue on GitLab
In GitLab by [Gitlab user @knownexus] on Aug 1, 2018, 10:12
Summary
If, when a build fails, the user quits instead of continuing, the artifact will not be pushed
Steps to reproduce
Build a project that fails,
When given the options of (t)terminate, (q)quit, (c)continue
select q
Check for the artifact in the cache
The artifact should be missing
What is the expected correct behavior?
The failed build artifact should be cached even when the quit option is selected
Possible fixes
One option is to have the artifact be cached at the point of the build failing, so at the point of choosing whether or not to continue, it is already cached
Other relevant information

BuildStream version affected: /milestone %BuildStream_v1.4

In GitLab by [Gitlab user @LaurenceUrhegyi] on Aug 1, 2018, 12:42
marked this issue as related to #21

In GitLab by [Gitlab user @LaurenceUrhegyi] on Aug 1, 2018, 12:56
removed the relation with #21

In GitLab by [Gitlab user @LaurenceUrhegyi] on Aug 1, 2018, 12:56
marked this issue as related to #76

In GitLab by [Gitlab user @knownexus] on Aug 2, 2018, 15:15
removed the relation with #76

In GitLab by [Gitlab user @Qinusty] on Aug 2, 2018, 15:28
Failed to reproduce with a simple failing project

In GitLab by [Gitlab user @richardmaw-codethink] on Sep 24, 2018, 17:14
I had a test for this when I made the changes.
This test now passes, so it looks like some other changes made it start working.
I'll submit the change to add the regression test.

In GitLab by [Gitlab user @richardmaw-codethink] on Sep 24, 2018, 17:19
mentioned in commit b536b22b1fe301479e8f6938ad18ba2dfc248ee3

In GitLab by [Gitlab user @richardmaw-codethink] on Sep 24, 2018, 17:22
mentioned in merge request !824

In GitLab by [Gitlab user @richardmaw-codethink] on Sep 27, 2018, 16:16
mentioned in commit d2ea306908c90d83e3798e2be42236bb77c0a48b

In GitLab by [Gitlab user @richardmaw-codethink] on Sep 27, 2018, 16:42
closed via merge request !824

In GitLab by [Gitlab user @richardmaw-codethink] on Sep 27, 2018, 16:42
mentioned in commit c128429ada3f8c35e7ac9f96db0516f74f1f560a

In GitLab by [Gitlab user @juergbi] on Feb 20, 2019, 06:21
reopened

In GitLab by [Gitlab user @juergbi] on Feb 20, 2019, 06:39
Reopening as this doesn't actually work, as far as I can tell. The test fails when run on its own:
tox -- --integration tests/integration/cachedfail.py::test_push_cached_fail[quit]

>           assert share.has_artifact('test', 'element.bst', cli.get_element_key(project, 'element.bst'))
E           AssertionError: assert None
[...]
tests/integration/cachedfail.py:164: AssertionError

The test passes if test_push_cached_fail[continue] ran earlier in the same test session, which is always the case in CI and thus we don't see the issue in CI. However, it frequently fails when running integration tests in parallel and the underlying issue remains.

In GitLab by [Gitlab user @juergbi] on Feb 20, 2019, 06:43
mentioned in commit 5ebd70320b2cac70ce9e5e15ecd0c6b3ffe1bb6b

In GitLab by [Gitlab user @juergbi] on Feb 20, 2019, 06:44
mentioned in merge request !1167

In GitLab by [Gitlab user @juergbi] on Feb 20, 2019, 06:55
mentioned in commit 670ac47962a2696851d9d628d9827500d7c5f2c7

In GitLab by [Gitlab user @tpollard] on Dec 2, 2019, 12:23
marked this issue as related to #1225

In GitLab by [Gitlab user @tristanvb] on Dec 9, 2020, 08:58
It looks like this comment at least has been fixed over time.
Currently the test in question does:
    if on_error == "quit":
        pytest.xfail("https://gitlab.com/BuildStream/buildstream/issues/534")

And the test body seems to be corrected, possibly by the introduction of the create_artifact_share() context manager there.

In GitLab by [Gitlab user @juergbi] on Dec 9, 2020, 09:11
It still fails for me when running the test on its own. Removing the xfail line I get:
tests/integration/cachedfail.py:136: AssertionError
[...]
FAILED tests/integration/cachedfail.py::test_push_cached_fail[quit] - AssertionError: assert None
================================================== 1 failed in 7.02s ==================================================

You see the test succeed with the tox command line from my previous comment?

This is closely related to #160

After discussing this in the meeting yesterday, it is worth mentioning that whether this is a bug is not very clear.
Clearly, it is desirable that if a build fails, it is uploaded to a cache by default (default strategy is --on-error quit).
This quit means to process any ongoing jobs and exit - which BuildStream clearly does correctly.
If we want this to work in an improved manner, it raises some questions:

When running bst build:

When a build job fails, should that artifact be uploaded even when instructed to quit
When a build job fails, should all artifacts which were built in this session still be pushed, even if those have not been scheduled yet and we have been instructed to quit ?

When running bst push:

When a push job fails, should we ignore the instruction to quit ?
When a push job fails, should we have a double standard and obey the instruction to quit even though it is contrary to bst build behavior ?

Perhaps there is something intuitive here which is to relate the command name with the queue performing that action and to infer that the --on-error is related to the imperative of that command ?
In other words:

When running bst pull and a pull fails, or any job placed before the pull queue fails, we cease queuing jobs into the pull queue and any queues before the pull queue, but we continue to process jobs in queues that post process pull jobs

It is intentional that this bst pull feels unnatural, there happens to not be any post processing to pull actions

When running bst build and a build fails, or any job placed before the build queue fails (e.g. pull or the fallback to fetch), we cease queuing jobs into the build queue and any queues before the build queue, but we continue to process jobs in queues that post process build jobs, e.g. push

With this approach, we can encode one of the scheduler queues to be the imperative queue and treat the --on-error quit strategy generically for all commands, in a way which appears to make most sense to the user, given the context of the command they are running.
Would this make sense ?


Create a Statistics Section

[x] create a statistic sections
[x] by asking IA to apply all title
[x] make it responsive for all devices
[x] try to make a small animation over there

Done ✅


Thoroughly test Camping::Server

Right now Camping::Server is untested. It does a lot of heavy lifting for Camping. In fact when we call bundle exec camping It's really Camping::Server that is run.
Camping Server inherits from Rackup::Server, I think we should take rigorous inspiration from the testing being done over there to write our tests. Some good starting points are here: https://github.com/rack/rackup/blob/main/test/spec_server.rb and here: https://github.com/rack/rackup/blob/main/test/helper.rb.

This is well underway. I've got Camping::Server being tested the same way that Rackup is tested. Next on our list is:

[ ] Test that Server Runs the initializers in /kindling before running Camping and setting up the apps.
[ ] Ensure that middleware is properly set up for the Server.
[ ] Document the Kindling behavior.


12_02_2023 update

Updated the README.md with new sections for BioImage Analysis lectures, resources, and tested tools
Added information about open access books and papers related to BioImage Analysis, and Image.sc Forum
Added example notebooks for LTEE, Wildlife detection, and Smear counting
Added a section about communities with links to four forums
Updated links for papers on image analysis accuracy and precision
Added a section about tools for reproducibility and updated the link to the paper "Avoiding Twisted Pixels"
Added information about The Turing Way and Zero-to-Binder, and link to ChatGPT
Added two references to relevant papers and a reference to the Metrics Reloaded framework
Tested pyTFM and Cell ACDC, and added descriptions of them to the README.md


Minimum configuration requirements to run mediapipe in Web, Android, iOS.

Description of issue (what needs changing)
Device specifications for mediapipe to run on Web, Android and iOS
Clear description
I am looking for the minimum configuration requirements to run MediaPipe effectively on Android, iOS, and Web devices.     Could you please provide details on the following for each platform?    Hardware Specifications:    CPU   RAM   Storage   GPU (specific brands or models, if any)     Software Specifications:    Minimum OS version Required   dependencies or libraries   Minimum browser versions for Web     Additional Information:    Performance benchmarks, if available   Optimization recommendations for lower-end devices    Thank you!
Correct links
No response
Parameters defined
No response
Returns defined
No response
Raises listed and defined
No response
Usage example
No response
Request visuals, if applicable
No response
Submit a pull request?
No response

Hardware Specifications:
CPU
RAM
Storage
GPU (specific brands or models, if any)
Software Specifications:
Minimum OS version Required
dependencies or libraries
Minimum browser versions for Web
Additional Information:
Performance benchmarks, if available
Optimization recommendations for lower-end devices
Thank you!

Can you please reply me for this question?

Hi @JhansiPyla28,
Unfortunately, we don't have the specific data you are looking for at this moment. However, We would be happy to discuss your needs further and see if we can find a way to assist you.

Thank you for your response.
Could you please provide any examples of the lowest-end devices on which MediaPipe has been successfully used? Additionally, have you encountered any devices where MediaPipe did not work due to hardware limitations? If so, could you share those specifications?

Hi @JhansiPyla28,
Apologies for the delay in our response. Currently, we lack the necessary data because MediaPipe's different Task APIs—such as Vision, Text, Audio, and Gen AI—each require specific environments. For example, Gen AI tasks need a real device with newer processors, while some Vision, Text, and Audio tasks cannot run on emulators or simulators. Based on discussions with our team, documenting this is currently challenging due to limited bandwidth. However, we can mark this issue as a feature request and share it with the team, though it may not be available soon.
Thank you!!


requests 2.18.1 with proxies throw SSLError: ("bad handshake: SysCallError(-1, 'Unexpected EOF')",)

Hi,
When I use requests 2.18.1 with proxies, it throw SSLError: ("bad handshake: SysCallError(-1, 'Unexpected EOF')",)
Scenario 1
Debian GNU/Linux 8
Python 3.6.1
OpenSSL 1.0.1t
pip list:
certifi (2017.4.17)
cryptography (2.0)
ndg-httpsclient (0.4.2)
pip (9.0.1)
pyasn1 (0.2.3)
pycparser (2.18)
pyldap (<IP_ADDRESS>)
pyOpenSSL (17.1.0)
PySocks (1.6.7)
requests (2.18.1)
requests-toolbelt (0.8.0)
setuptools (36.0.1)
six (1.10.0)
urllib3 (1.21.1)
My code:
import requests
proxies={'http':'socks5://<IP_ADDRESS>:8388', 'https': 'socks5://<IP_ADDRESS>:8388'}
r=requests.get('https://twitter.com',proxies=proxies)

Error message:
  File "/venv/lib/python3.6/site-packages/requests/adapters.py", line 514, in send
    raise SSLError(e, request=request)
requests.exceptions.SSLError: ("bad handshake: SysCallError(-1, 'Unexpected EOF')",)

When I degrade requests=2.11.1
The error gone.
Scenario 2
MacOS Sierra
Python 3.6.1
OpenSSL 1.0.2l
pip list:
The same as above
It also return the same error message
And also when I degrade requests=2.11.1
The error gone.
I want to know what the reason is, help me~ thanks

This is almost certainly because we removed 3DES from our default cipher suite list. Try following the steps in this blog post to see if that resolves your issue.

Thanks, it resolved my problem


Missing 4.1.0 in CocoaPods

Good afternoon,
We are still on Swift 2.2 and noticed there is a minor update 4.1.0, however this version has not been pushed to Cocoapods. Is it possible to have this version pushed? Or, is the change non-essential?
Thank you.

Pushed.
-> RNCryptor (5.0.1)
   Cross-language AES Encryptor/Decryptor data format.
   pod 'RNCryptor', '~> 5.0.1'
   - Homepage: https://github.com/rnapier/RNCryptor
   - Source:   https://github.com/rnapier/RNCryptor.git
   - Versions: 5.0.1, 4.1.0, 4.0.0, 4.0.0-beta.1, 3.0.1, 3.0.0, 2.2, 2.1, 2.0,
   1.1 [master repo]

I'd had some problems with CocoaPods, but the team finally get me setup correctly.


Improve command parsing and error handling

Codecov Report

Merging #175 (9cb586f) into master (7f739b6) will increase coverage by 1.15%.
The diff coverage is 89.60%.

@@             Coverage Diff              @@
##             master     #175      +/-   ##
============================================
+ Coverage     58.41%   59.56%   +1.15%
- Complexity      599      634      +35
============================================
  Files           121      125       +4
  Lines          2561     2629      +68
  Branches        251      250       -1
============================================
+ Hits           1496     1566      +70
+ Misses          975      964      -11
- Partials         90       99       +9

Impacted Files
Coverage Δ

...java/seedu/address/logic/commands/RedoCommand.java
0.00% <0.00%> (ø)

.../address/logic/commands/task/PurgeTaskCommand.java
0.00% <0.00%> (ø)

.../seedu/address/logic/parser/TaskCommandParser.java
0.00% <0.00%> (ø)

...ser/exceptions/ArgumentContainsSlashException.java
0.00% <0.00%> (ø)

...dress/logic/parser/task/FindTaskCommandParser.java
0.00% <0.00%> (ø)

...ic/parser/exceptions/TooManyPrefixesException.java
50.00% <33.33%> (-50.00%)
:arrow_down:

.../address/logic/parser/NoArgumentCommandParser.java
44.44% <50.00%> (-16.67%)
:arrow_down:

.../seedu/address/logic/parser/AddressBookParser.java
80.00% <75.00%> (ø)

.../seedu/address/logic/parser/FindCommandParser.java
62.50% <75.00%> (-37.50%)
:arrow_down:

...dress/logic/parser/task/ListTaskCommandParser.java
81.81% <75.00%> (+2.87%)
:arrow_up:

... and 40 more

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 7f739b6...9cb586f. Read the comment docs.


Add NftNamespace.getMintedNfts()

This PR adds the getMintedNfts() syntactic sugar method to fetch all the NFTs the provided owner address has minted. It uses getAssetTransfers to first get the corresponding transfers, then calls getNftMetadataBatch on the resulting transfers to get the underlying NFTs.
Had to do some refactoring to be able to use CoreNamespace methods in the NftNamespace.

Current dependencies on/for this PR:

main

PR #233   👈

PR #241

This comment was auto-generated by Graphite.


When an assert fires FGenericPlatformMisc::RaiseException is tracked instead than the actual error

Environment
How do you use Sentry?
Sentry SaaS (sentry.io)
Which version of the SDK?
0.16.0
How did you install the package? (Git-URL, Assetstore)
Git Download
Which version of Unreal?
5.3.2
Is this happening in Unreal (editor) or on a player like Android, iOS, Windows?
Linux Server
Steps to Reproduce

Run a server
Observe that instead than the assert FGenericPlatformMisc::RaiseException is tracked as the issue instead

Expected Result
The assert is the captured event in Sentry
Actual Result
The default raise exception is captured and the assert is "lost"
Any logs or screenshots
Log cuts off at:
[2024.03.12-14.00.37:849][466]LogOutputDevice: Warning:
When just after that the following occurs on the actual session log:
[2024.03.12-15.48.57:139][448]LogSentrySdk: flushing session and queue before crashpad handler
[2024.03.12-15.48.57:139][448]LogSentrySdk: invoking `on_crash` hook
[2024.03.12-15.48.57:140][448]LogSentrySdk: sending envelope
[2024.03.12-15.48.57:140][448]LogSentrySdk: serializing envelope into buffer
[2024.03.12-15.48.57:140][448]LogSentrySdk: handing control over to crashpad
CommonUnixCrashHandler: Signal=11
[2024.03.12-15.48.57:300][448]LogCore: === Critical error: ===
Unhandled Exception: SIGSEGV: invalid attempt to read memory at address 0x0000000000000008

[2024.03.12-15.48.57:300][448]LogCore: Fatal error!

Thank you, we'll check this on our end.
Btw is this issue something you've encountered just after upgrading to 0.16.0 or it was there previously as well?

Hey @tustanivsky It's always been a thing as far as I know, however, we skipped from 0.8.0 to 0.16.0 so unsure if there is a regression in-between those versions that brought it back if this has been fixed before.

Just to get it right @Edstub207: You're asserting something and running into the thing that was supposed to be asserted right afterward? Are you able to provide us with a minimal repro?

@bitsandfoxes Yeah, when we hit an assert Sentry tracks FGenericPlatformMisc::RaiseException - Which is a generic bucket in Unreal and doesn't actually track the assert itself.
As a result we also don't have the full logs sent to Sentry either, because it's sending the logs at the time of FGenericPlatformMisc::RaiseException not whatever the assert actually is, which properly logs/outputs just after FGenericPlatformMisc::RaiseException.

I think this is also related to #489 and #503. Basically, there's a whole bunch of situations when several top callstack frames of completely different events/errors could be the same which hides their origin and prevents them from being grouped properly at Sentry. I've been researching some alternative approaches of attaching only relevant callstack part to captured events lately and about to test those on my end to see whether it'll help to resolve the above issue.

@Edstub207 I've created a draft PR which is supposed helping to resolve this issue. Currently fix works only for Win/Linux yet if the suggested approach appears to be viable porting it to other platforms should be pretty straightforward. The corresponding plugin package can be downloaded from our CI here so if you could give it a try sometime we'd really appreciate your feedback.

@tustanivsky I will give it a try as well. We are on windows :)

I've tried this on our setup,
For asserts and other crashes, this seems to work well.
However, to ensure on Linux servers we are no longer getting any new issues in Sentry.
I've not done too much digging into this, but it seems to work well on Windows clients & seems to display slightly more info on Sentry issues. (The issue name is now "assertion failed", the Function name is rendered next to the issue name)
@tustanivsky Has the behavior been verified on Linux on your end? If so, this might be a setup issue on our end.

Thanks for the heads up @Tobias-Nilsson-Sharkmob, this seemed to work as expected on Linux but I'll double-check on my side and let you know.
Just wanted to clarify a few things here:

Is this behavior specific to Linux Server only?
For this configuration asserts/crashes events are captured as usual and it's only the ensures not getting uploaded to Sentry?

Hey @Tobias-Nilsson-Sharkmob, I've managed to reproduce this issue with ensures not being uploaded to Sentry too. It looks that UE handles them separately from asserts/crashes bypassing our events-capturing mechanism. Apparently there's still a way to hook in that process so that ensures can be intercepted and reported properly. I'll experiment with it a bit more and let you know.

Hi!
I've verified that ensures works properly now!
It does however seem the SentrySubsystemDesktop::CaptureEnsure culls one too many frames, I've changed this from 8 to 7 and get the behavior I would expect.
Any reason for ending 1 frame before the function with the ensure?
Thanks for getting this fixed quickly!

@Tobias-Nilsson-Sharkmob Thank you for the timely feedback! Which Unreal version and platform you're on? I suppose for older UE versions that generic callstack part which we're cutting off could differ so that's something we have to consider separately. I tested this only with UE 5.3 Win/Linux and so far everything seemed to work as expected.

Hey!
Tested on Windows & Linux for Unreal 5.1.
This might explain the difference, might be good with a code switch depending on the engine version in that case for the final push.
I'll get this running on our Main and see if any issues pop up.
Again, thanks for the help!

Got it, I'll make some extra tests with different UE versions to see how we can handle this.

Hello again!
We've been running this for a while now, and these changes seem to have exposed some underlying issues-
Since ensures can happen from different threads, when FSentryOutputDevice::Serialize may create Breadcrumb UObjects via AddBreadcrumbWithParams.
This breaks since there is a chance that the game thread is running garbage collection when this happens triggering "Unable to create new object: %s %s.%s. Creating UObjects while Collecting Garbage is not allowed"
This may also break in SentryScopeDesktop::AddBreadcrumb, since two threads can edit the internal list at the same time.
For our usage, we may simply switch USentryBreadcrumb from an UObject to a UStruct since we have no need for the UFunctions on that type.

I'll add our testing as well, as while Tobias + I are from the same studio, we're on different projects.
We rolled out this change but had to back it out due to it causing a crash which wasn't fatal without the changes - Potentially related to the Multhreaded stuff Tobias mentioned. The crash is in our code, pending a fix, but we intend on taking the changes back in once that's resolved. The brief time we had it available there where no obvious issues, although I would most likely wait for a resolution on the issue raised by Tobias before rolling out.

@Tobias-Nilsson-Sharkmob @Edstub207 Thanks for the heads up and providing the above details! I'll look into that and try to add some threading considerations

Hey @tustanivsky any update on this?

Hey @Edstub207, we will revisit this sometime next week and let you know once there are any updates. Tobias made some great points above regarding how threading issues may be resolved so I'll check if we can adopt these to make things moving faster.
Thank you for your patience.

@Edstub207 @Tobias-Nilsson-Sharkmob we're looking forward to merging #559 which is supposed to fix the threading issues mentioned earlier. Also, the suggested solution for assertion/ensure events grouping problem now supports Android/Apple and should be available after #537 passes the review


⚠ Bofrost.be has degraded performance

In 1e40e79, Bofrost.be (https://www.bofrost.be) experienced degraded performance:

HTTP code: 200
Response time: 1732 ms

Resolved: Bofrost.be performance has improved in 8f72b55 after 6 minutes.


Update zh-HANT.coffee

update the part of general

Hi, @ArthurLu! Thanks for your translations.

Hi, @Imperadeiro98 . Did you know the reason why I could not correctly merge my commit?

What do you mean?

I mean that I always get "Failure: The Travis CI build failed"

Yeah, it is not working correcly for any commit at the moment.


Bug report: Cannot resume training from a model trained with ddp_spawn strategy.

🐛 Bug

Encountered this bug, when trying to continue training from a model trained with ddp_spawn strategy.
To Reproduce

Please notice two things: 1) multi-GPU training 2) use RAdam/AdamW/etc. optimizer to replicate the bug (because SGD will not create any problem)
import os

import torch
from torch.utils.data import DataLoader, Dataset

from pytorch_lightning import LightningModule, Trainer
from pytorch_lightning.callbacks import ModelCheckpoint

class RandomDataset(Dataset):
    def __init__(self, size, num_samples):
        self.len = num_samples
        self.data = torch.randn(num_samples, size)

    def __getitem__(self, index):
        return self.data[index]

    def __len__(self):
        return self.len

num_samples = 10000

class BoringModel(LightningModule):
    def __init__(self):
        super().__init__()
        self.layer = torch.nn.Linear(32, 2)

    def forward(self, x):
        return self.layer(x)

    def training_step(self, batch, batch_idx):
        loss = self(batch).sum()
        self.log("train_loss", loss)
        return {"loss": loss}

    def validation_step(self, batch, batch_idx):
        loss = self(batch).sum()
        self.log("valid_loss", loss)

    def test_step(self, batch, batch_idx):
        loss = self(batch).sum()
        self.log("test_loss", loss)

    def configure_optimizers(self):
        return torch.optim.RAdam(self.layer.parameters(), lr=0.1)

def run():
    train_data = DataLoader(RandomDataset(32, 64), batch_size=2)
    val_data = DataLoader(RandomDataset(32, 64), batch_size=2)

    checkpoint_callback = ModelCheckpoint(save_last=True, save_top_k=1, monitor="valid_loss", mode="min", filename="best")

    model = BoringModel()
    trainer1= Trainer(
        gpus=-1,
        default_root_dir=os.getcwd(),
        limit_train_batches=1,
        limit_val_batches=1,
        limit_test_batches=1,
        num_sanity_val_steps=0,
        max_epochs=1,
        enable_model_summary=False,
        strategy="ddp_spawn",
        callbacks=[checkpoint_callback]
    )
    trainer1.fit(model, train_dataloaders=train_data, val_dataloaders=val_data)
    trainer2= Trainer(
        gpus=-1,
        default_root_dir=os.getcwd(),
        limit_train_batches=1,
        limit_val_batches=1,
        limit_test_batches=1,
        num_sanity_val_steps=0,
        max_epochs=2,
        enable_model_summary=False,
        strategy="ddp_spawn",
        callbacks=[checkpoint_callback]
    )
    trainer2.fit(
        model,
        train_dataloaders=train_data,
        val_dataloaders=val_data,
        ckpt_path=os.path.join(os.getcwd(), "lightning_logs/version_0/checkpoints/last.ckpt")
    )

if __name__ == "__main__":
    run()

Expected behavior
Run to the end without any error message.
Error message
-- Process 3 terminated with the following error:
Traceback (most recent call last):
  File "/usr/local/lib/python3.7/dist-packages/torch/multiprocessing/spawn.py", line 59, in _wrap
    fn(i, *args)
  File "/usr/local/lib/python3.7/dist-packages/pytorch_lightning/plugins/training_type/ddp_spawn.py", line 208, in _wrapped_function
    result = function(*args, **kwargs)
  File "/usr/local/lib/python3.7/dist-packages/pytorch_lightning/plugins/training_type/ddp_spawn.py", line 236, in new_process
    results = trainer.run_stage()
  File "/usr/local/lib/python3.7/dist-packages/pytorch_lightning/trainer/trainer.py", line 1289, in run_stage
    return self._run_train()
  File "/usr/local/lib/python3.7/dist-packages/pytorch_lightning/trainer/trainer.py", line 1319, in _run_train
    self.fit_loop.run()
  File "/usr/local/lib/python3.7/dist-packages/pytorch_lightning/loops/base.py", line 145, in run
    self.advance(*args, **kwargs)
  File "/usr/local/lib/python3.7/dist-packages/pytorch_lightning/loops/fit_loop.py", line 234, in advance
    self.epoch_loop.run(data_fetcher)
  File "/usr/local/lib/python3.7/dist-packages/pytorch_lightning/loops/base.py", line 145, in run
    self.advance(*args, **kwargs)
  File "/usr/local/lib/python3.7/dist-packages/pytorch_lightning/loops/epoch/training_epoch_loop.py", line 193, in advance
    batch_output = self.batch_loop.run(batch, batch_idx)
  File "/usr/local/lib/python3.7/dist-packages/pytorch_lightning/loops/base.py", line 145, in run
    self.advance(*args, **kwargs)
  File "/usr/local/lib/python3.7/dist-packages/pytorch_lightning/loops/batch/training_batch_loop.py", line 88, in advance
    outputs = self.optimizer_loop.run(split_batch, optimizers, batch_idx)
  File "/usr/local/lib/python3.7/dist-packages/pytorch_lightning/loops/base.py", line 145, in run
    self.advance(*args, **kwargs)
  File "/usr/local/lib/python3.7/dist-packages/pytorch_lightning/loops/optimization/optimizer_loop.py", line 219, in advance
    self.optimizer_idx,
  File "/usr/local/lib/python3.7/dist-packages/pytorch_lightning/loops/optimization/optimizer_loop.py", line 266, in _run_optimization
    self._optimizer_step(optimizer, opt_idx, batch_idx, closure)
  File "/usr/local/lib/python3.7/dist-packages/pytorch_lightning/loops/optimization/optimizer_loop.py", line 386, in _optimizer_step
    using_lbfgs=is_lbfgs,
  File "/usr/local/lib/python3.7/dist-packages/pytorch_lightning/core/lightning.py", line 1652, in optimizer_step
    optimizer.step(closure=optimizer_closure)
  File "/usr/local/lib/python3.7/dist-packages/pytorch_lightning/core/optimizer.py", line 164, in step
    trainer.accelerator.optimizer_step(self._optimizer, self._optimizer_idx, closure, **kwargs)
  File "/usr/local/lib/python3.7/dist-packages/pytorch_lightning/accelerators/accelerator.py", line 339, in optimizer_step
    self.precision_plugin.optimizer_step(model, optimizer, opt_idx, closure, **kwargs)
  File "/usr/local/lib/python3.7/dist-packages/pytorch_lightning/plugins/precision/precision_plugin.py", line 163, in optimizer_step
    optimizer.step(closure=closure, **kwargs)
  File "/usr/local/lib/python3.7/dist-packages/torch/optim/optimizer.py", line 88, in wrapper
    return func(*args, **kwargs)
  File "/usr/local/lib/python3.7/dist-packages/torch/autograd/grad_mode.py", line 28, in decorate_context
    return func(*args, **kwargs)
  File "/usr/local/lib/python3.7/dist-packages/torch/optim/radam.py", line 128, in step
    eps=group['eps'])
  File "/usr/local/lib/python3.7/dist-packages/torch/optim/_functional.py", line 436, in radam
    exp_avg.mul_(beta1).add_(grad, alpha=1 - beta1)
RuntimeError: Expected all tensors to be on the same device, but found at least two devices, cuda:0 and cuda:3!

cc @justusschock @kaushikb11 @awaelchli @akihironitta @rohitgr7

Hi @circlecrystal, could you fill up the bug report template? https://github.com/PyTorchLightning/pytorch-lightning/blob/master/.github/ISSUE_TEMPLATE/bug_report.md

Encountered this bug, when trying to continue training from a model trained with ddp_spawn strategy.

Sure, I will do that. I`m still trying to isolate the issue and replicate it with minimal code.

Further update: I tried to investigate this issue a little bit further, and found the root cause of the bug is that "the self.state of optimizer is not on the same device as model.device" in multi-GPU & dpp_spawn & resumed training.

One more thing: This fix is also a solution to a previous unanswered issue report months ago:
https://github.com/PyTorchLightning/pytorch-lightning/discussions/11435

Hello
I can verify that the issue reproduces on 1.5.10, but it does NOT reproduce on master and runs to completion without error.
On master, ddp_spawn internals have changed a lot and device setup is now very well aligned with the regular ddp.
In summary, this will be fixed in Lightning 1.6. There will be no 1.5.11 release but 1.6 and pre-release is coming soon.
Read here if you want to try installing from master.


Fix Example - 1

Example - 1 (which wasn't exactly working right out of the box before) has been fixed.
Locally running this on my linux64 machine, I haven't had any issues. Would appreciate it if someone could test this out on another platform too, and let me know.
Opening this PR to the add_docs branch since I've also taken the liberty of updating the documentation for example-1 accordingly.

Should fix #52 and #54.


Uncaught TypeError: interval.unref is not a function

Uncaught TypeError: interval.unref is not a function

Useless, this is missing all relevant info


API/Docs POST: /containers/create explain configuration structure

It would be super helpful if the documentation for this endpoint explained or listed a small note about what each of the parameters actually do and what the possible values for properties who's values are objects.
I am aware that this is the same object gleamed from docker inspect however to my knowledge this structure isn't precisely described in any part of the documentation.
For example, the documentation has the following text:
 {
         "Hostname":"",
         "User":"",
         "Memory":0,
         "MemorySwap":0,
         "AttachStdin":false,
         "AttachStdout":true,
         "AttachStderr":true,
         "PortSpecs":null,
         "Tty":false,
         "OpenStdin":false,
         "StdinOnce":false,
         "Env":null,
         "Cmd":[
                 "date"
         ],
         "Image":"base",
         "Volumes":{
                 "/tmp": {}
         },
         "WorkingDir":"",
         "DisableNetwork": false,
         "ExposedPorts":{
                 "22/tcp": {}
         }
    }

I think we should denote what the possible values of the properties such as ExposedPorts, Volumes, and Cmd in the section for this endpoint, or describe the configuration structure elsewhere and link to it from here, and similiar endpoints that utilize it like the inspection endpoint (/containers/(id)/json)

I see there's an open ticket for documenting the "output" as well (https://github.com/docker/docker/issues/1366) Just read that a new help is hired https://github.com/docker/docker/issues/254#issuecomment-71093443 @fredlf ? :smile:

@thaJeztah Yes, help is on the way and API docs will be one of the very first things she tackles. We are painfully aware of this backlog!

@fredlf no rush, I know there's a judge workload resting on your shoulders. Just politely "pinging" you here-and-there if I think issues could be related or picked up simultaneously.
I could try to start on this myself, but would have to do a bit of research, as I don't use the API directly.

Closing since these are now documented for the last few API versions.


Configure handshake timeout separately from session disconnect grace period

Why
We were magically computing a handshake timeout by dividing the session disconnect by 1000, which in production lead to a handshake timeout of 15ms (as session disconnect grace period is set to 15sec), which is pretty optimistic since RTT can be on the order of 100s of ms sometimes.
Instead of computing this magically, let's allow it be configured explicitly and set it to a default of 10s which matches what we have set in repl-it-web.
What changed

Add handshake_timeout_ms config with a default of 10s

Test plan

Ideally we see less handshake timeout errors in prod

Current dependencies on/for this PR:

main:

PR #77 👈

This comment was autogenerated by Freephite.

for reference, us-east4 <-> us-central1 latency is 28ms median https://console.cloud.google.com/net-intelligence/performance/global-dashboard?project=replit-web&pageState=("performanceDashboardTraffic":("v":"internal"),"performanceDashboardMetric":("v":"latency"),"pdNetworkTierState":("n":"NETWORK_TIER_UNSPECIFIED"),"performanceDashboardRegions":("regions":"[\"us-central1\",\"us-east4\"]")) lol

discussed offline about the possibility of adding a test.

added a test

Turns out dividing by 1000 was to convert from ms to sec, not to magically pick a good value here. But still this PR makes it more explicit and adds a test so worth landing.


move OapSqlBase.g4 out of spark source directory

What changes were proposed in this pull request?
Move OapSqlBase.g4 out of the spark source directory, since we have done the sql grammar decouple. Cherry-pick from #1127
How was this patch tested?
existing ut.

cc @zhixingheyi-tian @LuciferYang cherry-pick from branch-1.0


Upgrade Aether and wagon

This upgraded aether and maven to a more recent version.
change was trivial and all tests still pass.
the only change required was to adopt to
https://github.com/apache/maven-wagon/commit/1a005f1c3fe7492c10b06567738453118f1c15b6

this does double the size of the shaded jar, probably I missed an updated exclusion

Ok, maven 3.3 includes guava, so I dial back on that upgrade a bit.

Give me some time to review. We use aether 1.0.2 in large product and I could test the upgrade there. You can read a story about Aether here - Aether Resolver was forked as https://maven.apache.org/resolver/ and soon (pax-url 3?) we'll use it.

AFAIK Eclipse Aether is abandoned and will not receive any major or even minor updates.

Aether is gone and Maven took it over since Maven doesn't use Ivy. Speaking
of which, Ivy itself is back under development, so all those forks out
there (e.g., in Gradle, SBT, Jenkins, etc.) might be able to stop
maintaining them, too.
On 16 June 2017 at 04:50, Łukasz Dywicki<EMAIL_ADDRESS>wrote:

AFAIK Eclipse Aether is abandoned and will not receive any major or even
minor updates.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/ops4j/org.ops4j.pax.url/pull/25#issuecomment-308983843,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAwS6xswPXZKxt9zUUGe7LJ0T3N63i9wks5sEk_XgaJpZM4N69Qy
.

--
Matt Sicker<EMAIL_ADDRESS>

which doesn't contradict at least a minor version bump.
Is anyone actively working on "pax-url-resolver"? I asked for that some time ago, but got no feedback.

This change adds two imports to pax-url-aether bundle:

com.google.common.base,
com.google.common.collect,

and some itests stop passing

I don't have free cycles to investigate this, but I'd like not to have the requirement on external guava library. private-packaging it isn't a good idea too IMO.

@grgrzybek i thought i fixed that. let me check

its no longer on maven dependency:tree, any advice on how to find our where bnd gets this from?

I totally would like to have pax-url-aether ship way less private repacked classes. 3mb is not what it should be.

The failed test was itest/src/it/itest-aether-osgi when running in eclipse-3.6 profile (aether-osgi-eclipse-3.6 execution of maven-invoker-plugin).
I just have:
13:09:06.796 [main] ERROR o.o.p.e.n.i.NativeTestContainer - Bundle [org.ops4j.pax.url.mvn_2.5.3.SNAPSHOT [12]] is not resolved

After debugging, I saw that it has additional imports. And I don't think adding Guava to pax-exam test is good fix ;)

I totally would like to have pax-url-aether ship way less private repacked classes. 3mb is not what it should be.

I kind of agree. But otoh, relying on other bundles would make pax-url-aether not that fundamental bundle... And it's used to install all bundles declared using mvn: protocol...
There's https://ops4j1.jira.com/browse/PAXURL-148 which is about splitting pax-url-aether, but I think it's not that good idea...

for other bundles we always also have a dedicated shaded all-inclusive bundle.
@jbonofre or @gnodet ... do you happen to know if this is already the case for pax-url-mvn or just for another one?

I'd leave pax-url-aether as shaded bundle only - otherwise how would you install the required dependencies? using file: protocol directly?

@grgrzybek ... the question right now is, where is the sweet spot of a slimmed down and a all-in bundle :)
Just trying to find that.

For me the key is:

is the library we're private-packaging prepared by developers who cares about OSGi at all?
is the library actively and transparently maintained? (Apache, Pax) or not (Sonatype, Codehaus forked to strange repo)

In addition - pax-url-aether is special, because after pax-url-aether, we can use mvn: protocol and we like to use it ;)

Finally I had some time and fixed it here: 3a6f4ac84855e86fcba4fbf64a64df9f15232acb

The issue is https://ops4j1.jira.com/browse/PAXURL-348, fixed in pax-url 2.6.0 (not released yet) - all tests pass

wow, this is big @grgrzybek
Thanks a ton


Remove content on loading an image as an embedded resource

The section on loading embedded images in XAML (https://learn.microsoft.com/en-us/dotnet/maui/user-interface/controls/image#load-an-embedded-image-in-xaml) should be removed. It's carried over from Forms, and has been superseded by MauiImage.
See https://github.com/dotnet/maui/issues/8666 for more info.

Document Details
⚠ Do not edit this section. It is required for learn.microsoft.com ➟ GitHub issue linking.

ID: cb4d16da-8c0f-5b7e-54ee-1fe36c549837
Version Independent ID: cb4d16da-8c0f-5b7e-54ee-1fe36c549837
Content: Image - .NET MAUI
Content Source: docs/user-interface/controls/image.md
Product: dotnet-mobile
Technology: dotnet-maui
GitHub Login: @davidbritch
Microsoft Alias: dabritch

Associated WorkItem - 90898

@dotMorten What's the scenario?


Rate limited by github when trying to execute digital-ocean-agent with anthropic provider.

gptscript version - v0.0.0-dev-51fd2b32-dirty
Steps to reproduce the problem:

Execute  digital-ocean-agent with anthropic provider with --disable-cache  - gptscript --default-model 'claude-3-5-sonnet-20240620 from github.com/gptscript-ai/claude3-anthropic-provider' --debug  --disable-cache github.com/gptscript-ai/digital-ocean-agen

Rate limited by github and following error is reported:

2024/06/27 13:27:05 failed resolving ./databases.gpt from https://raw.githubusercontent.com/gptscript-ai/digital-ocean-agent/691fc6f31f061a5ecd78a2a9573c67f89c699c46/tool.gpt: failed resolving databases* from ./openapi.yaml from https://raw.githubusercontent.com/gptscript-ai/digital-ocean-agent/691fc6f31f061a5ecd78a2a9573c67f89c699c46/databases.gpt: failed resolving github.com/gptscript-ai/credential as api.digitalocean.combearer_auth with GPTSCRIPT_API_DIGITALOCEAN_COM_BEARER_AUTH as env and "Please provide a value for the GPTSCRIPT_API_DIGITALOCEAN_COM_BEARER_AUTH environment variable" as message and "bearer token" as field from https://raw.githubusercontent.com/gptscript-ai/digital-ocean-agent/691fc6f31f061a5ecd78a2a9573c67f89c699c46/openapi.yaml: failed to get GitHub commit of gptscript-ai/credential at HEAD (fallback error failed to find remote "https://github.com/gptscript-ai/credential.git" as "HEAD"): 403 Forbidden {"message":"API rate limit exceeded for <IP_ADDRESS>. (But here's the good news: Authenticated requests get a higher rate limit. Check out the documentation for more details.)","documentation_url":"https://docs.github.com/rest/overview/resources-in-the-rest-api#rate-limiting"}
**Note ** -

This issue is not seen in my setup when executing the scripts without --disable-cache option.
This issue is also seen when GITHUB_AUTH_TOKEN is set. But sometimes  I have seen this issue also not happen sometimes with  GITHUB_AUTH_TOKEN set.
Digital Ocen agent works fine and does not hit this issue when testing with gpt-4o with or without --disable-cache option.

@sangee2004 I merged changes that I think will fix this.

Tested with gptscript version - v0.0.0-dev-a42c9e31-dirty
Not hitting github rate limits when executing github.com/gptscript-ai/digital-ocean-agent with anthropic provider and using --disable-cache option.


Seg fault restarting stack frame in debugger

I'm running the debugger in vs-code and just tried to restart the top most stackframe (of the ones you can restart).
The following seg fault occurred:

===== CRASH =====
si_signo=Segmentation fault(11), si_code=1, si_addr=(nil)
version=2.16.0-80.1.beta (beta) (Mon Dec 13 11:59:02 2021 +0100) on "linux_x64"
pid=3199510, thread=3199760, isolate_group=main(0x558a82541800), isolate=main(0x558a824a6000)
isolate_instructions=558a810962e0, vm_instructions=558a810962e0
Stack dump aborted because InitialRegisterCheck failed.
Aborted (core dumped)

Unfortunately this report does not contain any information to help us figure out what happened.


Vulnerability in js-yaml dependency

Description
The js-yaml dependency in graphqlgen's package.json is reported to be a vulnerability.
See https://www.npmjs.com/advisories/813.
Steps to reproduce

Create a blank project.
npm install --save graphqlgen
npm audit

Expected results
npm audit reports no vulnerabilities.
Actual results
npm audit reports a high severity vulnerability:
  High            Code Injection

  Package         js-yaml

  Patched in      >=3.13.1

  Dependency of   graphqlgen [dev]

  Path            graphqlgen > js-yaml

  More info       https://npmjs.com/advisories/813

Versions

graphqlgen: 0.5.1
OS name and version: Windows 10

I would recommend to simply update the js-yaml dependency.
Also using ^ when declaring dependencies can often avoid such kind of bug, as the patch in the dependency's repo could automatically be loaded, without making changes to graphqlgen.

Another moderate vulnerability is reported, also caused by js-yaml:
https://www.npmjs.com/advisories/788

I also have this high vulnerability plus 67 vulnerabilities (63 low, 3 moderate, 1 high). But they are all dev packages, just us graphqlgen and Jest which I believe when it is built, the final product wont use this packages w/  vulnerabilities.
What do you think? Is that right?


Feat(eos_designs): interface storm-control feature can be set per platform

Change Summary
vEOS-LAB platform does not support storm-control configuration as of EOS 4.26 - remove the feature from the rendered configuration.

Related Issue(s)
Fixes #1194
Component(s) name
arista.avd.eos_designs
Proposed changes

Use same approach as for queue_monitor_length_notify to disable the feature on the "default" platform
platform_settings:
  - platforms: [ < Arista Platform Family >, < Arista Platform Family > ]
    feature_support:
      interface_storm_control: < true | false | default -> true >

How to test

Use a port profile that enables storm-control:
port_profiles:
  ##### parent port-profiles to be inherited by device related port-profiles #####
  port_profile_DOT1Q_EDGE:
    mode: trunk
    spanning_tree_bpdufilter: false
    spanning_tree_bpduguard: true
    spanning_tree_portfast: edge
    storm_control:
      broadcast:
        level: 1
        unit: percent
      multicast:
        level: 1
        unit: percent
      unknown-unicast:
        level: 1
        unit: percent

Checklist
User Checklist

N/A

Repository Checklist

[x] My code has been rebased from devel before I start
[x] I have read the CONTRIBUTING document.
[x] My change requires a change to the documentation and documentation have been updated accordingly.
[ ] I have updated molecule CI testing accordingly. (check the box if not applicable)

Hi folks (@ClausHolbechArista @titom73 @carlbuchmann ),
any implementation feedback from your side on this? As this is a blocker in our QA environment.

So I would proceed and rather add the vEOS-LAB platform as additional platform?

So I would proceed and rather add the vEOS-LAB platform as additional platform?

Just leave the defaults file untouched and we will add that extra platform in a separate PR. (already on it's way)

@ClausHolbechArista ah okay - so it looks like I just need to stay put? I can do that!

@ClausHolbechArista ah okay - so it looks like I just need to stay put? I can do that!

Please fix the other comments. Thanks

Thank you guys for renaming switch -> adapter_switch in 9c0bb3e562aa86310cd766791952daff5209ecb0 - that makey it much easier to access the switch key and my hack with set .. is obsolete.


px-app-nav modifies the navItems object

I ran into some unexpected issues in my application because I was populating px-app-nav from an object which I reference elsewhere; this caused some unanticipated effects elsewhere in the application when px-app-nav modified the object to store state. Most examples I've found populate the nav with an array literal, so my use case may be somewhat unusual.
I ended up fixing the problem by using lodash to deep clone my array object and binding the clone.
Note that this occurred despite the fact that I did not use a two-way data binding. That's not too surprising, given that it is technically modifying the referenced object, not the reference, but I still find this somewhat counterintuitive. If state is going to be stored by modifying the navItems object, I would expect the element to clone the object and modify the new object instead.
Expected behavior
Nav element avoids modifying navItems object.
Actual behavior
Nav element stores state by modifying navItems object, which can cause unexpected results if other elements have references to the object.
Steps to reproduce
Bind an object rather than using an array literal to supply nav items; watch the object from somewhere else where it can be examined (e.g. set it as a property of some other element, and inspect the element from the browser console). Note that the object is modified.
Environment
All.
Proposed fix
In the ready and _observeChanged callbacks, rather than directly modifying the object, clone it and save the clone to a private _navItems property, and store px-app-nav's state in this object.
If others agree that this is a legitimate issue and a good fix, I'm happy to submit a pull request to do it.

Damon is part of a Pod I lead at the DTH where we're leveraging this element. As he stated in his proposed fix, we're prepared to take on the development ourselves and contribute it back, but didn't want to do the work until we confirm that the PX- team is open to the change. We wanted to run it by you all before putting the work in as we may try to find another way around it if the pull request won't be accepted.

Hello @dsiefert @murone please feel free to contribute a solution back; please provide sufficient test coverage with it.  Thank you

Would it not be as simple as switching notify: true to false on navItems? Might be massively oversimplifying it there :)
That said, this would be API breaking so would require a major bump. I can't with any certainty say that people don't rely on this feature of notifying changes back...
You should always be able to rationalise a good web components' state by its properties too... Moving to what you propose would mean that would no longer be possible.
Which is a long way of me saying, I'm not entirely sure it is a good idea but don't have much to support this hunch ;-)

This issue is for an outdated version of px-app-nav (v1.x). The new version has a revamped API and explicitly avoids mutating the items passed in by the developer.


Possibility to opt-out of steps

Thanks for this great buildpack!
We used your buildpack to simply install bun, install dependencies with bun and then use the node buildpack to run the remaining actions. This is needed, because we're in the middle of a migration phase and not everything is bun compatible yet - and it yet won't be for quite some time I think.
Unfortunately, after your recent changes, we need to use an older version of your buildpack because the latest one is breaking our heroku build process. Get me right, the changes you did were great, but they simply doesn't work (yet) for us!
Would there be any chance that we could add possibility to opt-out of some steps?
Maybe via a config file?
Let me know what you think.

For me, it's basically skipping any action except of installing bun itself and running bun install.
So, I'd like to be able to skip:

has_heroku_prebuild_script
has_build_script
has_heroku_postbuild_script

Basically, everything that is here:
https://github.com/jakeg/heroku-buildpack-bun/blob/75d47baa2075efa17f4f48bdc2fd4480b33582dd/bin/compile#L69-L89
But maybe it makes sense to also be able to opt-out of bun install.
That would make this buildpack even more flexible for projects that don't use bun yet as a package manger.

This should now be possible with files named .skip-bun-[xxx] eg .skip-bun-heroku-prebuild. Please do confirm if you have a chance to try it out.

@jakeg Works like a charm! Thanks a ton!! ❤


Add Scalar UDF Note about Cached/Constant Folding

Per https://github.com/duckdb/duckdb/issues/7773, Scalar UDFs return the same result even for non-deterministic functions.
In my opinion: This, at least, should be documented as a 0.8.0 limitation on the appropriate page, probably Python Function API

This is no longer the case, through side_effects you can communicate whether the method is deterministic or not
https://duckdb.org/docs/api/python/function#side-effects


[$250] [HOLD for payment 2024-04-03] [Simplified Collect] [Workflows] Connect bank account label is too small in Workspace > Workflows

If you haven’t already, check out our contributing guidelines for onboarding and email<EMAIL_ADDRESS>to request to join our Slack channel!

Version Number: 1.4.54-1
Reproducible in staging?: Y
Reproducible in production?: Y
If this was caught during regression testing, add the test name, ID and link from TestRail: NA
Email or phone of affected tester (no customers):  NA
Logs: https://stackoverflow.com/c/expensify/questions/4856
Expensify/Expensify Issue URL: NA
Issue reported by: @shawnborton
Slack conversation: https://expensify.slack.com/archives/C049HHMV9SM/p1710853970755619
Action Performed:

Go to Workspace settings and enable Workflows.
From here, enable "Make or track payments"

Expected Result:
The default label for "Connect bank account" should be in 15px font size.
Actual Result:
The label is in 13px font.
Workaround:
NA, pertains to font-size.
Platforms:

Which of our officially supported platforms is this issue occurring on?

[ ] Android: Native
[ ] Android: mWeb Chrome
[ ] iOS: Native
[ ] iOS: mWeb Safari
[x] MacOS: Chrome / Safari
[x] MacOS: Desktop

Screenshots/Videos

Upwork Automation - Do Not Edit

Upwork Job URL: https://www.upwork.com/jobs/~01058f2b7b8cc824a4
Upwork Job ID:<PHONE_NUMBER>483059200
Last Price Increase: 2024-04-26

@shubham1206agra thanks for your proposal but this will be dealt internally as it's a small change and I've assigned myself right from the start.

The PR that introduced the bug has been identified. Link to the PR: https://github.com/Expensify/App/pull/37629
The offending PR has been commented on, pointing out the bug it caused and why, so the author and reviewers can learn from the mistake. Link to comment: https://github.com/Expensify/App/pull/37629/files#r1551133005
A discussion in #expensify-bugs has been started about whether any other steps should be taken (e.g. updating the PR review checklist) in order to catch this type of bug sooner. Link to discussion: N/A
Determine if we should create a regression test for this bug. Yes
If we decide to create a regression test for the bug, please propose the regression test steps to ensure the same bug will not reach production again.

Regression Test Proposal

Go to Workspace settings and enable Workflows.
From here, enable "Make or track payments"
Verify that the Connect bank account label is 15px font size

Do we agree 👍 or 👎

@kevinksullivan Friendly bump for payment :bow:

@kevinksullivan Another friendly bump :bow:

@kevinksullivan Would you be able to process payment on this please? Thanks 🙏

Just to note that this issue is from before the change in the default payment, so this one should be $500 cc @kevinksullivan.

offer sent @jjcoffee lmk when you accept
https://www.upwork.com/jobs/~01c41af72ecd13262c

@kevinksullivan Accepted, thanks!

Not overdue, just finalizing payments.

all set!


Missing contribute.md file.

I am a GSSoc'24 contributor. I would like to add this file. Could you please assign this to me?

I would like to work on this issue. Please assign it to me.

can you assign this task to me. I have already done the Readme for this repo and would like to contribute further

@hasmithagunda123 please assign this task to me

@hasmithagunda123 i would like to work for this issue under GSSOC'24.

I would like to work on this, please assign this to me

I would like to work on this please assign this to me

@hasmithagunda123, in the label level 1, could you please remove the space-bar between 'level' and '1'. Only if the label is of the form 'level1', will our contributions towards this task fetch us points towards the leaderboard of gssoc. Thank you


Add option for insecure registry

I'm not sure why there is no insecure option here.

/lgtm
/approve


Improve/clarify log reporting/tracking (ES System Log and EVS Event Log)

Is your feature request related to a problem? Please describe.
EVS event logging reports LogFullFlag, LogMode, and LogOverflowCounter.

The log is an array of CFE_EVS_LongEventTlm_t of size CFE_PLATFORM_EVS_LOG_MAX so each entry has a slot
In either discard or overwrite, once the log is filled LogFullFlag is set to true, and LogOverflowCounter is incremented for each additional message (so you can tell how many messages were dropped or added after being full).
Note LogCount is maintained internally but is not in tlm (counts number of entries in the log, clamps at max)

ES syslog reports SysLogBytesUsed, SysLogSize, SysLogEntries, and SysLogMode.

The log is a more freeform char array SystemLog of size CFE_PLATFORM_ES_SYSTEM_LOG_SIZE
In discard, the log is "full" when CFE_PLATFORM_ES_SYSTEM_LOG_SIZE - SysLogBytesUsed is less than  CFE_TIME_PRINTED_STRING_SIZE
SysLogBytesUsed is actually set to the internal SystemLogEndIdx that is the end of the last message (so when overwriting this will drop back down to a low number)
SysLogEntries increments whenever a message is written, so if in overwrite it's not actually the number of entries in the log but the number of entries that have ever been written to the log
There are return codes (CFE_ES_ERR_SYS_LOG_TRUNCATED and CFE_ES_ERR_SYS_LOG_FULL), but they are only returned in discard mode, and not available in tlm
SysLogSize is the full size of the log, CFE_PLATFORM_ES_SYSTEM_LOG_SIZE

Describe the solution you'd like
Numerous misnomers and inconsistencies in log management should be fixed/clarified, within the context of the actual differences in these logs (char array vs event array).
Describe alternatives you've considered
None
Additional context
Code review
Requester Info
Jacob Hageman - NASA/GSFC
ping @dmknutsen @olamoo13

@dmknutsen @alamoo13 - looks like there's a couple options to knowing when the system log is full based on the current implementation
In discard mode:

you could create an event from the test app that gets sent if write to sys log returns CFE_ES_ERR_SYS_LOG_FULL
you could check for SysLogBytesUsed > CFE_PLATFORM_ES_SYSTEM_LOG_SIZE (or SysLogSize) - CFE_TIME_PRINTED_STRING_SIZE
If you could store values/do math, for a new log entry if SysLogEntries doesn't change it's full
In overwrite mode:
If you could store values/do math, whenever SysLogBytesUsed goes back down that means you've looped
without math, maybe cause a bunch of entries, then check for a SysLogBytesUsed value to be below some reasonable amount, and cycle if needed

@dmknutsen @olamoo13 - if you wanted to get really fancy, the test app could subscribe to the ES housekeeping and do the math for you.  Basically add a command to "fill the log", and it could continue creating syslog messages until the hk packet values show it's full.  That would move the logic into the app.  I'm not a huge fan of this approach (test app should be as simple as possible), but it's a way to get it done for now.


Bug fixes + some code clean up

Fixed bugged animations of characters that don't start with bf but still being used as player 1 (they basically behave the same as other bf characters now)
Fixed vocals disappearing on Optimization mode incase last note on bf turn was missed
Renamed Stage Positioning Debug to Stage Debug State
Removed ability to access Stage Debug State on Optimization mode (they don't see stage anyway so what's the point)
Fixed crashes connected with Stage Testing variable not being set to false in some cases
Added more info to Stage class for skids
Removed useless Bopeebo mid-song event
Cleaned up code overall

based

o huh didn't think about doing the check that way, sounds a lot more reliable

Btw just realized that first one also fixes bf character as opponent, cuz he wouldn't idle properly after singing first note if not for this fix


ROX-13502: Remove the circular dependency between cluster datastore init and cscc notifier init

Description
A recent change brought in the cscc init dependency on cluster datastore singleton causing a circular dependency leading to a central hang during upgrade of a cluster with a cscc notifier. This is a regression and a release blocker. Fix was to remove the init dependency and initialize the cluster singleton closer to use, in the AlertNotify path instead of cscc init.
Checklist

[x] Investigated and inspected CI test results
[x] ~Unit test and regression tests added~
[x] ~Evaluated and added CHANGELOG entry if required~
[x] ~Determined and documented upgrade steps~
[x] ~Documented user facing changes (create PR based on [openshift/openshift-docs]~(https://github.com/openshift/openshift-docs) and merge into rhacs-docs)

Testing Performed
Manually upgraded staging cluster, which had central  in hung state to PR image. Results from staging, upgrade successful, and central is back up.
ksanchet@ksanchet-mac:~/go/src/github.com/stackrox/stackrox$ kc get pods -n stackrox
NAME                                 READY   STATUS    RESTARTS           AGE
admission-control-7759746db9-49mf5   1/1     Running   0                  9d
admission-control-7759746db9-bb2vl   1/1     Running   0                  9d
admission-control-7759746db9-w2496   1/1     Running   0                  9d
central-7cddcb694d-rkm8r             0/1     Running   1 (3h7m ago)       6d23h
collector-fvhtb                      2/2     Running   264 (27m ago)      9d
collector-rchwl                      2/2     Running   265 (27m ago)      9d
collector-s5srl                      2/2     Running   267 (27m ago)      9d
monitoring-789c644886-v2mcd          2/2     Running   0                  9d
scanner-5b74ddd776-96f8c             1/1     Running   0                  9d
scanner-5b74ddd776-p7lg5             1/1     Running   0                  9d
scanner-db-5cfbbdbf69-48smb          1/1     Running   0                  9d
sensor-c84cbb987-nv6fz               1/1     Running   1451 (3m47s ago)   9d
ksanchet@ksanchet-mac:~/go/src/github.com/stackrox/stackrox$ kubectl -n stackrox set image deploy/central central=quay.io/rhacs-eng/main:3.72.x-585-g9fab31d377
deployment.apps/central image updated
ksanchet@ksanchet-mac:~/go/src/github.com/stackrox/stackrox$ kc get pods -n stackrox
NAME                                 READY   STATUS    RESTARTS          AGE
admission-control-7759746db9-49mf5   1/1     Running   0                 9d
admission-control-7759746db9-bb2vl   1/1     Running   0                 9d
admission-control-7759746db9-w2496   1/1     Running   0                 9d
central-56b795c65f-kzvhc             1/1     Running   0                 3m13s
collector-fvhtb                      2/2     Running   265 (18m ago)     9d
collector-rchwl                      2/2     Running   266 (18m ago)     9d
collector-s5srl                      2/2     Running   268 (18m ago)     9d
monitoring-789c644886-v2mcd          2/2     Running   0                 9d
scanner-5b74ddd776-96f8c             1/1     Running   0                 9d
scanner-5b74ddd776-p7lg5             1/1     Running   0                 9d
scanner-db-5cfbbdbf69-48smb          1/1     Running   0                 9d
sensor-c84cbb987-nv6fz               1/1     Running   1455 (7m2s ago)   9d

Thanks for fixing this.


idf.py set-target esp32 : Failed to resolve component 'cbor' (IDFGH-6826) (MEGH-3225)

Environment
ubuntu@ubuntu:~/esp-rainmaker/examples/switch$ idf.py set-target esp32
Adding "set-target"'s dependency "fullclean" to list of commands with default set of options.
Executing action: fullclean
Build directory '/home/ubuntu/esp-rainmaker/examples/switch/build' not found. Nothing to clean.
Executing action: set-target
Set Target to: esp32, new sdkconfig created. Existing sdkconfig renamed to sdkconfig.old.
Running cmake in directory /home/ubuntu/esp-rainmaker/examples/switch/build
Executing "cmake -G Ninja -DPYTHON_DEPS_CHECKED=1 -DESP_PLATFORM=1 -DIDF_TARGET=esp32 -DCCACHE_ENABLE=0 /home/ubuntu/esp-rainmaker/examples/switch"...
-- Found Git: /usr/bin/git (found version "2.32.0")
-- Component directory /home/ubuntu/esp-rainmaker/components/esp-insights does not contain a CMakeLists.txt file. No component will be added
-- The C compiler identification is GNU 8.4.0
-- The CXX compiler identification is GNU 8.4.0
-- The ASM compiler identification is GNU
-- Found assembler: /home/ubuntu/.espressif/tools/xtensa-esp32-elf/esp-2021r2-patch3-8.4.0/xtensa-esp32-elf/bin/xtensa-esp32-elf-gcc
-- Detecting C compiler ABI info
-- Detecting C compiler ABI info - done
-- Check for working C compiler: /home/ubuntu/.espressif/tools/xtensa-esp32-elf/esp-2021r2-patch3-8.4.0/xtensa-esp32-elf/bin/xtensa-esp32-elf-gcc - skipped
-- Detecting C compile features
-- Detecting C compile features - done
-- Detecting CXX compiler ABI info
-- Detecting CXX compiler ABI info - done
-- Check for working CXX compiler: /home/ubuntu/.espressif/tools/xtensa-esp32-elf/esp-2021r2-patch3-8.4.0/xtensa-esp32-elf/bin/xtensa-esp32-elf-g++ - skipped
-- Detecting CXX compile features
-- Detecting CXX compile features - done
-- Building ESP-IDF components for target esp32
CMake Error at /home/ubuntu/esp/esp-idf/tools/cmake/build.cmake:197 (message):
  Failed to resolve component 'cbor'.
Call Stack (most recent call first):
  /home/ubuntu/esp/esp-idf/tools/cmake/build.cmake:231 (__build_resolve_and_add_req)
  /home/ubuntu/esp/esp-idf/tools/cmake/build.cmake:512 (__build_expand_requirements)
  /home/ubuntu/esp/esp-idf/tools/cmake/project.cmake:422 (idf_build_process)
  CMakeLists.txt:16 (project)

-- Configuring incomplete, errors occurred!
See also "/home/ubuntu/esp-rainmaker/examples/switch/build/CMakeFiles/CMakeOutput.log".
cmake failed with exit code 1

IDF version (run git describe --tags to find it):

ubuntu@ubuntu:~/esp/esp-idf$ git describe --tags
v5.0-dev-1662-g2ac0942dfb

Build System:         [Make|CMake|idf.py]
Compiler version

ubuntu@ubuntu:~/esp/esp-idf$ xtensa-esp32-elf-gcc --version
xtensa-esp32-elf-gcc (crosstool-NG esp-2021r2-patch3) 8.4.0
Copyright (C) 2018 Free Software Foundation, Inc.
This is free software; see the source for copying conditions.  There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.

Operating System: Linux.
Using an IDE?: No
Power Supply: USB

Problem Description
When running idf.py set-target esp32 inside esp-rainmaker/examples/switch/ I get above error message
I tried to reinstall esp-idf multiple times, but error still persistent

I've transferred this issue to esp-rainmaker project.
cbor component has been moved from ESP-IDF into idf-extra-components repository in https://github.com/espressif/esp-idf/commit/ebaca79557c3de530dacfd56ac9e5fd10caf8295. It is now available via the IDF component manager: https://components.espressif.com/component/espressif/cbor.
To fix the issue in Rainmaker project, it is necessary to add idf_component.yml file and define a dependency on cbor component.


check devicename on signup for non-ascii characters

Per CORE-8221, non-ascii device names on signup can throw a misleading error when the server fails to parse. This PR catches those errors a little earlier with a more helpful message.
Before
Non-canonical JSON error dump signing up
After
Bad device name: MyGarbage🗑🔥DeviceName is not between 3 and 64 characters long; use a-Z, 0-9, space, plus, underscore, dash and apostrophe

Name the branch xgess/CORE-8221-your-comment-here or just xgess/CORE-8221

(No need to change the name, just for future reference; that triggers a JIRA hook to have it associated with the issue.)