Skip to content
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

Closed
4 of 6 tasks
jrbourbeau opened this issue Oct 25, 2022 · 25 comments
Closed
4 of 6 tasks

Release 2022.10.1 #283

jrbourbeau opened this issue Oct 25, 2022 · 25 comments
Labels

Comments

@jrbourbeau
Copy link
Member

jrbourbeau commented Oct 25, 2022

Release version 2022.10.1
Planned release date 2022-10-28
Status On-track
Release manager @jrbourbeau

Best effort

Try to close before the release but will not block the release

Blocker

Issues that would cause us to block and postpone the release if not fixed

Comments

cc @ian-r-rose @fjetter @quasiben @jakirkham

@douglasdavis
Copy link
Member

douglasdavis commented Oct 25, 2022

Digging a bit with the CLI issue..

After installing dask and distributed with conda-forge

If I run python -m dask...

$ python -m dask

shows what we want:

Usage: python -m dask [OPTIONS] COMMAND [ARGS]...

  Dask command line interface.

Options:
  --version   Show the version and exit.
  -h, --help  Show this message and exit.

Commands:
  docs       Open Dask documentation (https://docs.dask.org/) in a web browser.
  info       Information about your dask installation.
  scheduler  Launch a distributed scheduler.
  ssh        Launch a distributed cluster over SSH.
  worker     Launch a distributed worker attached to an existing SCHEDULER.

but

$ dask

shows

Usage: dask [OPTIONS] COMMAND [ARGS]...

  Dask command line interface.

Options:
  --version   Show the version and exit.
  -h, --help  Show this message and exit.

Commands:
  docs  Open Dask documentation (https://docs.dask.org/) in a web browser.
  info  Information about your dask installation.

$ python -m dask is running dask.__main__:main while $ dask is running dask.cli:cli. (note the pip(setuptools) installation uses dask.__main__:main). I think the conda-forge entry point should be dask.__main__:main

@douglasdavis
Copy link
Member

douglasdavis commented Oct 25, 2022

Opened a PR conda-forge/dask-feedstock#200 fixed in dask-core-feedstock!

@jakirkham
Copy link
Member

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

@jrbourbeau
Copy link
Member Author

I've opened this issue around requiring python<3.11 dask/dask#9605. If folks have thoughts on the topic I'd appreciate feedback on that issue.

@jrbourbeau
Copy link
Member Author

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 bokeh < 3 for dask and distributed given that we know there are compatibility issues with the bokeh=3 release scheduled to come out later today (cc @fjetter @crusaderky)

@mrocklin
Copy link
Member

@gjoseph92 @fjetter are we turning on task queuing on the scheduler by default in this release?

@gjoseph92
Copy link

No, it won't be ready in time. See dask/distributed#7213.

@jrbourbeau
Copy link
Member Author

jrbourbeau commented Oct 28, 2022

@gjoseph92
Copy link

@jrbourbeau not critical, but could be good to get dask/distributed#7224 in if CI passes and you have time to review.

@jrbourbeau
Copy link
Member Author

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

@gjoseph92
Copy link

No worries, queuing is still behind a feature flag so it's not too big of a deal.

@jrbourbeau
Copy link
Member Author

jrbourbeau commented Oct 28, 2022

@jrbourbeau
Copy link
Member Author

jrbourbeau commented Oct 29, 2022

Alright, PyPI and conda-forge packages are released.

We ran into a problem building the Python 3.8 dask-notebook image over in dask-docker (xref dask/dask-docker#255) due to an issue in the underlying jupyter/base-notebook notebook (xref jupyter/docker-stacks#1810). I've attempted a couple of possible fixes, but haven't gotten those build to work yet. I've proposed a temporary workaround in dask/dask-docker#256 where we drop Python 3.8 builds. This is a possible workaround, but admittedly feels a bit heavy handed. I'm on PTO next week -- @jacobtomlinson @jakirkham @charlesbluca could I ask you to handle docker images for this release by either finding an actual fix, or by merging the PR that temporarily drops Python 3.8 builds?

@jakirkham
Copy link
Member

FWIW commented on the upstream (Jupyter) issue.

@mrocklin
Copy link
Member

mrocklin commented Oct 31, 2022 via email

@mrocklin
Copy link
Member

Pushing out a hotfix #284

If there is anything I should know folks should jump in very soon.

@ian-r-rose
Copy link

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)

@jrbourbeau
Copy link
Member Author

jrbourbeau commented Oct 31, 2022

I think @gjoseph92 is comfortable including that change has he asked for it to be included in the 2022.10.1 release, but it just didn't make it in time (xref #283 (comment))

EDIT: queuing is also still behind a feature flag, so I think it's safe to move forward with that change included

@mrocklin
Copy link
Member

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?

@charlesbluca
Copy link
Member

could I ask you to handle docker images for this release by either finding an actual fix, or by merging the PR that temporarily drops Python 3.8 builds?

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.

@jakirkham
Copy link
Member

Would follow these steps for marking packages broken in conda-forge. Unfortunately I don't have bandwidth for this atm

@charlesbluca
Copy link
Member

Thanks @jakirkham! Opened up conda-forge/admin-requests#504 to request the packages be marked as broken

@jakirkham
Copy link
Member

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

@jakirkham
Copy link
Member

jakirkham commented Nov 2, 2022

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.

@jakirkham
Copy link
Member

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! 🙏

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

7 participants