-
Notifications
You must be signed in to change notification settings - Fork 165
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
Consistenty - IOError
vs EBADF
?
#798
Comments
ioquatix
changed the title
Consistenty - IOError vs EBADF?
Consistenty - Sep 11, 2024
IOError
vs EBADF
?
ioquatix
added a commit
to socketry/io-stream
that referenced
this issue
Sep 11, 2024
See <ruby/openssl#798> for more details.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
SSLSocket
error conditions are not consistent withIO
.io.close
followed byio.read
can result inEBADF
rather thanIOError
.sync_close
,io.close
followed byio.read
will hang. Even if the underlying IO is not closed, I don't think theSSLSocket
instance should continue to work after being closed?Reproduction:
Is this something we can improve?
The text was updated successfully, but these errors were encountered: