Merged
Conversation
Collaborator
|
This makes sense, while the Thanks for your investigative work to catch this @patrix58! ❤️ 🎉 RelatedRelevant upstream changes in the close_rpc() function, as changed ~3 months ago and then later ~3 years ago. This change makes sense as long as we use a version of distributed less than 3 years old in my mind, so should be fine to merge without further changes. |
consideRatio
approved these changes
Jul 21, 2022
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
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.
Missing await in client.py causes a warning when shutting down the cluster.
Test
Tested on Ubuntu 22.04 with Python 3.10, dask-gateway==2022.6.1 and Slurm backend.
Test script:
Actual output
The printed warning:
After
No warning is displayed, rpc close coroutine is awaited.