{{ message }}
bpo-30064: Fix asyncio loop.sock_* race condition issue#20369
Merged
1st1 merged 2 commits intoMay 27, 2020
Merged
Conversation
f65e373 to
a246122
Compare
May 25, 2020 20:20
1st1
reviewed
May 25, 2020
1st1
reviewed
May 25, 2020
1st1
approved these changes
May 26, 2020
Member
|
Thanks, Fantix! |
Sorry, something went wrong.
miss-islington
added a commit
that referenced
this pull request
May 27, 2020
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
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.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.
https://bugs.python.org/issue30064
This is reproducible by a
cancel()followed directly by a retry:This issue applies to all the
loop.sock_*methods. Without this PR, users could work it around by adding asleep(0):