Prevent update handling task pointers from being garbage collected, backport of #1328 #1331
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.
Description
This is a backport of #1328 to mitigate possible issues like #628, #927. As in #1328, this PR preserves asyncio
Task
pointers until the task is completed to ensureTask
will not be garbage collected and disappear. See recommendations in Python docs.Type of change
How Has This Been Tested?
Honestly, I don't have a v3-based bot with workload I have in v2. But want to admit once again, it's a pretty rare case and we're handling it as the docs says.
Test Configuration: