Uh oh!
There was an error while loading.Please reload this page.
- Notifications
You must be signed in to change notification settings - Fork33.3k
bpo-29711: Fix stop_serving in proactor loop kill all listening servers#431
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to ourterms of service andprivacy statement. We’ll occasionally send you account related emails.
Already on GitHub?Sign in to your account
Uh oh!
There was an error while loading.Please reload this page.
Conversation
mention-bot commentedMar 3, 2017
1st1 commentedMar 3, 2017
@Haypo Can you take a look at this PR? |
julien-duponchelle commentedAug 21, 2017
Can I do something to help ? |
vstinner left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others.Learn more.
LGTM.
vstinner commentedAug 21, 2017
I agree that it's plain wrong to cancel the "accept future" ofall listening servers. |
1st1 commentedOct 19, 2017
Could you please add a NEWS entry using blurb? |
asvetlov commentedDec 13, 2017
@noplay ping |
ca0f031 to42a07c5Comparejulien-duponchelle commentedDec 13, 2017
News entry added |
1st1 commentedDec 18, 2017
Could you please rebase your PR once again? |
42a07c5 to8f11cb3Comparejulien-duponchelle commentedDec 18, 2017
It's rebase |
Uh oh!
There was an error while loading.Please reload this page.
Current implementation of the asyncio Proactor event loop has an issue, when you stop a server it's cancel the futures of all other servers.
Original discussion:python/asyncio#496
https://bugs.python.org/issue29711