Conversation
Was apparently fine when the update occurred, but has changed since.
These were already reported upstream some months ago.
Looks like an expectation mismatch with aiohttp 3.8.5, we'll wait for upstream to catch up to that version.
I think this leads to a more reasonable dependency closure for this library.
https://github.com/pydata/xarray/releases/tag/v2023.03.0 https://github.com/pydata/xarray/releases/tag/v2023.04.0 https://github.com/pydata/xarray/releases/tag/v2023.04.1 https://github.com/pydata/xarray/releases/tag/v2023.04.2 https://github.com/pydata/xarray/releases/tag/v2023.05.0 https://github.com/pydata/xarray/releases/tag/v2023.06.0 https://github.com/pydata/xarray/releases/tag/v2023.07.0
https://github.com/jupyter-server/jupyter_server/releases/tag/v2.0.7 https://github.com/jupyter-server/jupyter_server/releases/tag/v2.1.0 https://github.com/jupyter-server/jupyter_server/releases/tag/v2.2.0 https://github.com/jupyter-server/jupyter_server/releases/tag/v2.2.1 https://github.com/jupyter-server/jupyter_server/releases/tag/v2.3.0 https://github.com/jupyter-server/jupyter_server/releases/tag/v2.4.0 https://github.com/jupyter-server/jupyter_server/releases/tag/v2.5.0 https://github.com/jupyter-server/jupyter_server/releases/tag/v2.6.0 https://github.com/jupyter-server/jupyter_server/releases/tag/v2.7.0
Introduced for sanic upgrade.
Introduced for a sanic bump
Has not been updated for Python 3.11.
This is so we can build tomlkit with poetry-core with running into an infinite recursion.
...into staging-next
gif-for-cli: support pillow 10
...into staging-next
...into staging-next
Man, copy&paste to five places is just great :-/ The referenced upstream patch should fix the compatibility, but it won't apply cleanly to this version, so I dropped the test.
12 tasks
12 tasks
12 tasks
...into staging-next
...into staging-next
...into staging-next
...into staging-next. Taken from PR #247814
Member
Author
|
Oh, I forgot to comment. Thank you all for the numerous fixes. Hundreds of builds remain regressed for sure, but I think we can take it to master now and (possibly) continue fixing in there. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
20 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Helpful links
https://hydra.nixos.org/job/nixpkgs/staging-next/unstable#tabs-constituents
https://hydra.nixos.org/job/nixos/staging-next-small/tested
https://hydra.nixos.org/jobset/nixpkgs/staging-next
https://hydra.nixos.org/jobset/nixos/staging-next-small
Mass breakages
(will be edited based on progress)