ssl: Give correct errno value for "timed out" exceptions #9006
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Incorrect error handling in send/recv would raise an OSError with an incorrect (negative) code.
It's likely that this bug was always happening in the Pico W implementation, which became the basis of the current shared implementation.
Push handling of WANT_{READ,WRITE} down into mbedtls_raise_error and use it in recv_into and send.
Tested by connecting to google.com:443, sending nothing, and trying to read a byte:
As desired, an exception
OSError: [Errno 116] ETIMEDOUT
occurred and the time delta value was 1.0 seconds.(tested on pycamera)
Closes: #8988