[issue30698] asyncio sslproto do not shutdown ssl layer cleanly

Andrew Svetlov added the comment: Agree -- resolution: -> duplicate stage: -> resolved status: open -> closed ___ Python tracker ___

[issue30698] asyncio sslproto do not shutdown ssl layer cleanly

Kumar Aditya added the comment: Since https://bugs.python.org/issue44011 is fixed now, this can be closed. @asvetlov -- nosy: +kumaraditya303 versions: +Python 3.11 -Python 3.5, Python 3.6, Python 3.7 ___ Python tracker

[issue30698] asyncio sslproto do not shutdown ssl layer cleanly

Manjusaka added the comment: Ping! Agree with Wei-Cheng. The leak still bothers me for times, and still bother for third-party like https://aiohttp.readthedocs.io/en/stable/client_reference.html#tcpconnector Yury, I think it's worth working on it. Using uvloop should not be a good idea for

[issue30698] asyncio sslproto do not shutdown ssl layer cleanly

Wei-Cheng Pan added the comment: The SSL connection still cannot close cleanly in 3.7.0. It will keep throwing read error during shutdown, so shutdown callback will never be called. I've been test this PR for a while, and at least it fixes my problem. Hope this PR can be included in 3.7.1, o

[issue30698] asyncio sslproto do not shutdown ssl layer cleanly

Yury Selivanov added the comment: Is this issue resolved now, or do we need to work on this? -- ___ Python tracker ___ ___ Python-bu

[issue30698] asyncio sslproto do not shutdown ssl layer cleanly

Change by Andrew Svetlov : -- nosy: +asvetlov ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.pyt

[issue30698] asyncio sslproto do not shutdown ssl layer cleanly

Grzegorz Grzywacz added the comment: No, this PR originally fix similar but different issue. However it also fix issue29406 as a side effect. -- ___ Python tracker ___ __

[issue30698] asyncio sslproto do not shutdown ssl layer cleanly

Alexander Mohr added the comment: @grzgrzgrz3, does this resolve the issue in https://bugs.python.org/issue29406 ? I'm guessing you based this PR on that issue. If so I'd like it merged ASAP as otherwise our prod services will be incompatible with all future python releases given the original

[issue30698] asyncio sslproto do not shutdown ssl layer cleanly

Grzegorz Grzywacz added the comment: No one yet responded, maybe this is unclear. I will clarify what is going on, why i made this change, what we gain from this and why this is not ideal solution. I will focus on ssl layer shutdown as this issue regards. We have connection asyncio <-> nginx

[issue30698] asyncio sslproto do not shutdown ssl layer cleanly

Changes by Alexander Mohr : -- nosy: +thehesiod ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.py

[issue30698] asyncio sslproto do not shutdown ssl layer cleanly

Changes by Grzegorz Grzywacz : -- pull_requests: +2320 ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://

[issue30698] asyncio sslproto do not shutdown ssl layer cleanly

New submission from Grzegorz Grzywacz: Asyncio on shutdown do not send shutdown confirmation to the other side. _SSLPipe after doing unwrap is calling shutdown callback where transportis closed and quit ssldata wont be sent. -- components: asyncio messages: 296295 nosy: grzgrzgrz3,