Fix "coroutine was never awaited" warnings #929
Draft
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.
Fix warnings such as the one below:
The fix requires introducing a fairly complex mechanism that checks for references to the UCP context and preemptively stop continuous progress when no listeners or endpoints are alive anymore. This is necessary because it's impossible to cancel a future once the event loop that owns it stops, which will happen in third-party projects where UCX-Py doesn't own the event loop, such as Distributed.
TODO: Verify how to still provide continuous progress for workers that do not make use of listeners, instead relying on
ucp.recv()
, which receives messages directly on the worker.