-
-
Notifications
You must be signed in to change notification settings - Fork 714
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
Starting a Local cluster in an existing jupyter notebook crashes #7536
Comments
I think I have the same issue - described on this post. |
you can avoid this issue for now by pinning If that does indeed help, this would make this issue a duplicate of #7515 Edit: another option besides downgrading would be to set the multiprocessing method to |
Thanks @jbusecke for the issue and @keewis for the context / workaround. To consolidate discussion, I'm going to close this as a duplicate of #7515. Also wanted to note that there's a new |
Pinning ipykernel to avoid issue raised in dask/distributed#7536 dask/distributed#7515
* Pin ipykernel>6.21.2 Pinning ipykernel to avoid issue raised in dask/distributed#7536 dask/distributed#7515 * [condalock-command] autogenerated conda-lock files --------- Co-authored-by: pangeo-bot <pangeo-bot@users.noreply.github.com>
Describe the issue:
I suspect that some recent updates to dask/distributed introduced a bug when using a LocalCluster in an existing notebook.
Minimal Complete Verifiable Example:
This conda environment is sufficient to reproduce the problem:
EDIT: the above actually works but we are not looking to use python 3.11 just yet.
this does not work:
which resolves to the following versions
Now if you open a new notebook with jupyterlab and execute the following code in a cell twice
the notebook cell throws a horrible long warning (which makes the notebook unresponsive for a while and maybe? crashes the jupyterlab)
I was able to extract this bit from the warning/error trace:
Which indicates to me that there is something incompatible happening between the notebook metadata and dask?
This bug currently prevents everyone at our Center to use a LocalCluster which is pretty bad for many of us. Does anyone know a workaround/fix for this? Thanks.
The text was updated successfully, but these errors were encountered: