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
StreamWriter.wait_closed() can hang indefinitely. #83939
Comments
Raising an issue that's impacting us on It appears that in some cases SSL unwrapping can cause Trio are particularly careful to work around this case, and have an extensive comment on it: https://github.com/python-trio/trio/blob/31e2ae866ad549f1927d45ce073d4f0ea9f12419/trio/_ssl.py#L779-L829 Originally raised via encode/httpx#634 Tested on:
|
Can reproduce in:
|
I am also seeing this in Python 3.8.6. I am not using SSL, but am simply calling |
Regarding my previous comment: I have never seen this in Python 3.7 (though I see that this particular bug is listed as being present there) so it may be a different underlying issue. |
See this issue on 3.9.6 |
On main branch with rewritten SSL implementation #75458 bpo-44011, this raises TimeoutError: -------------------------------------------------------------------------------- Traceback (most recent call last):
File "/workspaces/cpython/main.py", line 18, in <module>
asyncio.run(main())
^^^^^^^^^^^^^^^^^^^
File "/workspaces/cpython/Lib/asyncio/runners.py", line 44, in run
return loop.run_until_complete(main)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/workspaces/cpython/Lib/asyncio/base_events.py", line 645, in run_until_complete
return future.result()
^^^^^^^^^^^^^^^
File "/workspaces/cpython/main.py", line 14, in main
await writer.wait_closed()
^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/workspaces/cpython/Lib/asyncio/streams.py", line 344, in wait_closed
await self._protocol._get_close_waiter(self)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
TimeoutError: SSL shutdown timed out This issue has been fixed, it can be closed @asvetlov. |
Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.
Show more details
GitHub fields:
bugs.python.org fields:
The text was updated successfully, but these errors were encountered: