Fix when scheduler returns a tuple instead of a list#951
Merged
jacobtomlinson merged 2 commits intodask:mainfrom Mar 2, 2026
Merged
Fix when scheduler returns a tuple instead of a list#951jacobtomlinson merged 2 commits intodask:mainfrom
jacobtomlinson merged 2 commits intodask:mainfrom
Conversation
|
Any chance of getting a release with this fix? |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Closes #950
Looks like the distributed scheduler has started intermittently returning a tuple instead of a list when calling the
workers_to_close()RPC method.There is an assertion in
dask-kubernetesthat was added as part of some type narrowing in #881. This fails when the method returns a tuple. This PR works around this by converting tuples to lists.