[issue32219] SSLWantWriteError being raised by blocking SSL socket

Change by Kyle Altendorf : -- nosy: +altendky ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue32219] SSLWantWriteError being raised by blocking SSL socket

Nathaniel Smith added the comment: I don't know :-( After filing this upstream we started ignoring these exceptions, to make our CI less flaky: https://github.com/python-trio/trio/pull/365/files But unfortunately that means I don't know if we've been hitting them since then or not.

[issue32219] SSLWantWriteError being raised by blocking SSL socket

Christian Heimes added the comment: Nathaniel, is this still an issue with recent OpenSSL and Python versions? -- status: open -> pending ___ Python tracker ___

[issue32219] SSLWantWriteError being raised by blocking SSL socket

Nathaniel Smith added the comment: There's no timeout. The man page claims SSL_ERROR_WANT_WRITE can't happen on a blocking socket, but who knows... Re: EINTR, this is all happening in a child thread. On Linux, this would mean that it almost certainly isn't receiving any

[issue32219] SSLWantWriteError being raised by blocking SSL socket

Antoine Pitrou added the comment: You might want to add debugging code in _ssl__SSLSocket_shutdown_impl() (Modules/_ssl.c) and see what happens exactly. Does your socket have a timeout? If not, you may want to ask the OpenSSL mailing-list whether it's possible for

[issue32219] SSLWantWriteError being raised by blocking SSL socket

Nathaniel Smith added the comment: Oh darn, I restarted the 311618077 build on Travis and apparently that makes it delete the log. Well, it was the same traceback as the one that's left, but triggered by a different test. -- ___

[issue32219] SSLWantWriteError being raised by blocking SSL socket

New submission from Nathaniel Smith : I have a test case that sets up a blocking SSLSocket, and eventually calls unwrap() to do a proper SSL shutdown. Every once in a while, the test blows up, because unwrap() unexpectedly raises SSLWantWriteError. This is very unexpected for