Raise informative error when mixing futures between clients#2227
Merged
mrocklin merged 1 commit intodask:masterfrom Sep 5, 2018
Merged
Raise informative error when mixing futures between clients#2227mrocklin merged 1 commit intodask:masterfrom
mrocklin merged 1 commit intodask:masterfrom
Conversation
Previously when a future was used within a different client the client would just unpack the key and use it directly. Now we explicitly check that the future is being used with the correct client, and raise an informative error if this is not the case.
e0c2a41 to
175171c
Compare
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
1 participant
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.
Previously when a future was used within a different client the client
would just unpack the key and use it directly. Now we explicitly check
that the future is being used with the correct client, and raise an
informative error if this is not the case.