-
-
Notifications
You must be signed in to change notification settings - Fork 3
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Release 2022.05.2 #250
Comments
I'd like to get
in this release as well. They are a couple of fairly straightforward fixes that have already been approved, just waiting on CI to finish |
Just a note, the fix in the OP is in |
Looks like the remaining blockers were merged. Was there anything else needed before releasing? |
Nope, I think we're good. I've got a break in my calendar coming up and will start pushing out the release then |
JFYI am going to be out starting tomorrow. So won't be back until Tuesday (mentioning in the rare event other issues crop up) |
2022.05.2 is out on PyPI and conda-forge PRs are open
Thanks for the heads up -- hope you have a nice long weekend |
conda-forge packages and docker images are out now. Thanks all! |
Dask `2022.5.1` had a bug and a new release is out, this PR upgrades the dask pinning: dask/community#250 Authors: - GALI PREM SAGAR (https://github.com/galipremsagar) Approvers: - AJ Schmidt (https://github.com/ajschmidt8)
I wouldn't necessarily wait on the OSX builds. I'm +1 to just merging in
if you're ready to fire on the release.
…On Thu, May 26, 2022 at 1:03 PM jakirkham ***@***.***> wrote:
Just a note, the fix in the OP is in
—
Reply to this email directly, view it on GitHub
<#250 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AACKZTCFG3J2PS3PDST6PFLVL64GNANCNFSM5W6WCXMQ>
.
You are receiving this because you are subscribed to this thread.Message
ID: ***@***.***>
|
@mrocklin was that comment intended for a different issue? This one has been resolved for several months |
It appears that a bunch of very old comments-by-email recently got processed by GitHub and are being posted as new. |
Ah interesting. Thanks for the context! 🙏 |
A bug was introduced in the latest
distributed=2022.05.1
release (xref dask/distributed#6448). @jakirkham @quasiben are working on a fix now over in dask/distributed#6449 and @JacksonMaxfield has already confirmed that reverting dask/distributed#6333 also fixed the issue. I'd like to push out a patch release tomorrow either with the fix in dask/distributed#6449 (hopefully this can be merged soon) or my merging a revert commit for dask/distributed#6333 intodistributed
The text was updated successfully, but these errors were encountered: