-
-
Notifications
You must be signed in to change notification settings - Fork 727
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
LocalCluster crashed with: distributed.core - ERROR - 'tuple' object does not support item assignment #4625
Comments
Thanks for reporting and providing a nice minimal example @felix0097! I'm able to reproduce on the latest cc @madsbk @jakirkham if you have any thoughts. I was hoping that #4595 would have fixed this issue too, but I'm able to reproduce with the latest dev version of |
Yep this is duplicate of issue ( #3716 ). Would propose we close and track there |
@jakirkham just curious, is there any reason this would have recently (since the previous release) become a much more common issue? the linked issue is a year old but I haven't seen any of the errors from this issue until very recently. would be nice if there's a workaround for now to unblock upgrading to 2021.3 |
It looks like we're expecting a list here when getting a tuple. I suspect that this is due to msgpack always returning tuples for us. We should maybe not mutate this list, but instead make a new one? |
This maybe solve things? #4653 |
What happened:
Python programs crashes with the following error message:
What you expected to happen:
No error: persist or compute call returns as usual
Minimal Complete Verifiable Example:
Anything else we need to know?:
Without creating the LocalCluster and Client everything works as expected, so I would guess this issue has something to do with the LocalCluster
With dask version
2021.2
everything works correctlyEnvironment:
The text was updated successfully, but these errors were encountered: