-
-
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.10.1 #283
Comments
Digging a bit with the CLI issue.. After installing If I run
shows what we want:
but
shows
|
|
Thanks all for helping dig into the CLI issues! 🙏 Given the pain around that, would like to propose hardening the Click requirement in Dask going forward ( dask/dask#9595 ). Ideally would like to include that in this release |
I've opened this issue around requiring |
We haven't quite gotten dask/distributed#5648 over the finish line yet, so I'm going to push up PRs to put an upper bound of |
@gjoseph92 @fjetter are we turning on task queuing on the scheduler by default in this release? |
No, it won't be ready in time. See dask/distributed#7213. |
@jrbourbeau not critical, but could be good to get dask/distributed#7224 in if CI passes and you have time to review. |
Ah, sorry @gjoseph92 I need to start pushing out the release. Unfortunately I think that one will have to get in in the next release |
No worries, queuing is still behind a feature flag so it's not too big of a deal. |
2022.10.1 is out on PyPI and conda-forge PRs are open: |
Alright, PyPI and conda-forge packages are released. We ran into a problem building the Python 3.8 |
FWIW commented on the upstream (Jupyter) issue. |
Heads up: dask/dask#9609
Does anyone here have time to investigate what happened here with Bokeh?
It appears that we're affecting Airflow negatively.
…On Sat, Oct 29, 2022 at 3:53 AM jakirkham ***@***.***> wrote:
FWIW commented on the upstream (Jupyter) issue.
—
Reply to this email directly, view it on GitHub
<#283 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AACKZTFYPEGQJAQRJA6DSWLWFTQYXANCNFSM6AAAAAAROE5LGY>
.
You are receiving this because you commented.Message ID:
***@***.***>
|
Pushing out a hotfix #284 If there is anything I should know folks should jump in very soon. |
There isn't anything I'm aware of that would prevent a hotfix, though dask/distributed#7224 is a non-trivial change. Perhaps @gjoseph92 can comment on whether it's likely to be an issue (I suspect he'd be fine with it) |
I think @gjoseph92 is comfortable including that change has he asked for it to be included in the EDIT: queuing is also still behind a feature flag, so I think it's safe to move forward with that change included |
I've already chatted with @gjoseph92 and he confirmed. I've yanked this release from PyPI. Can someone (maybe @jakirkham) help with yanking from conda-forge channels? |
Any opposition to unblocking the 3.8 Docker builds locally with dask/dask-docker#257 until the upstream issue is resolved? This would involve patching the impacted Jupyter dockerfile, which could get hairy in the long run, but it doesn't seem like CI is running very often on dask-docker for this to be an issue. |
Would follow these steps for marking packages broken in conda-forge. Unfortunately I don't have bandwidth for this atm |
Thanks @jakirkham! Opened up conda-forge/admin-requests#504 to request the packages be marked as broken |
As to Jupyter docker-stacks, outlined a path forward in comment ( jupyter/docker-stacks#1810 (comment) ). If anyone has bandwidth to try, should be a couple line change |
Updating this thread, Charles' workaround was merged yesterday. Mamba released 1.0.0 early today. This subsequently fixed Jupyter docker-stacks ( jupyter/docker-stacks#1810 (comment) ). With that fixed, Charles reverted the workaround ( dask/dask-docker#260 ). Edit: Also merged Charles PR yesterday to mark conda-forge packages broken. |
Sounds like there is nothing more to do here. So going to close this out, but please feel free to reopen if I've missed something. Thanks all! 🙏 |
Best effort
Try to close before the release but will not block the release
bokeh=3
distributed#5648dask scheduler
not recognized as a valid command, despite suggestion fromFutureWarning
distributed#7176Client.restart_workers
method distributed#7154Blocker
Issues that would cause us to block and postpone the release if not fixed
bokeh=3
distributed#7173 (noting that this is no longer a blocker, even though the issue is still open as we've added temporary workarounds forbokeh=3
compatibility -- see the PRs linked in Release 2022.10.1 #283 (comment))Comments
cc @ian-r-rose @fjetter @quasiben @jakirkham
The text was updated successfully, but these errors were encountered: