-
Notifications
You must be signed in to change notification settings - Fork 5.5k
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
BaseIOStream.read_bytes
may raise incorrect exception type with OpenSSL 3.4.0
#3443
Comments
This sounds similar to #3357 (fixed in Tornado 6.4.1, can you confirm if you're already using that version?) We fixed that issue by altering one of our Or maybe the cpython |
FWIW Traceback:
|
Oh, also can confirm that |
In dask/distributed we're seeing a wrong exception being raised in one of our tests, see dask/distributed#8936
The test is closing the stream server side just after the connection has been established. We then assert that the client side notices this and is raising an appropriate error.
This issue seems to be linked to the new openssl version 3.4.0. With the new version we're seeing a
ssl.SSLError: [SYS] unknown error (_ssl.c:2580)
instead of aStreamClosedError
I don't have a minimal (tornado only) reproducer, yet. We can deal with this by loosening our exception handling but I wondered if there is something tornado can / wants to do
The text was updated successfully, but these errors were encountered: