-
Notifications
You must be signed in to change notification settings - Fork 558
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 our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Server fails to shutdown while persistent connections exist #180
Comments
Can you submit a PR to revert that commit and maybe write a unittest? |
I wrote a test and then reverted the 124e981, but the test still fails with uvloop. |
Thanks! |
…done" (MagicStack#180) This reverts commit 124e981.
Sorry, I noticed I hadn't removed the generated .c file. After running |
…done" (MagicStack#180) This reverts commit 124e981.
Can we have a bugfix release? |
Revert "Fix Server to wait in wait_closed() until all transports are done" This reverts commit 124e981.
Fixed in uvloop 0.11.1. Thanks for working on this! |
I noticed that my aiohttp server with uvloop==0.11.0 awaits until all connections (WebSocket, streaming, etc.) are closed. This behavior prevents us from performing aiohttp's graceful shutdown.
This problem doesn't occur with uvloop==0.10.2.
I'm suspecting the commit 124e981 because this change seems not to conform to the following spec:
The text was updated successfully, but these errors were encountered: