Skip to content

BaseIOStream.read_bytes may raise incorrect exception type with OpenSSL 3.4.0 #3443

@fjetter

Description

@fjetter

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 a StreamClosedError

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

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions