-
Notifications
You must be signed in to change notification settings - Fork 63
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
Unhandled EWOULDBLOCK errors breaking TlsStream #64
Comments
I can reproduce this reliably (as in, it never works) when I compile tiny with statically linked openssl-1.1.0g. |
@reading123 could you try again with latest tiny? ( |
Yay it works!! No errors here. |
Also, Merry Christmas! :) |
Good to hear. Merry Christmas to you too :) |
Originally reported by @reading123 on #61,
It seems like some
EWOULDBLOCK
errors are slipping through our error handlers and causingConn
methods to fail. The error message tiny prints is:I can't reproduce this so I'm not sure how to solve. As a starting point we should probably compare our
EWOULDBLOCK
handling with tokio-core's TcpStream https://github.com/tokio-rs/tokio-core/blob/master/src/net/tcp.rs .I also created the issue sfackler/rust-native-tls#63 but later it occured to me that if we do
EWOULDBLOCK
instream::tcp::TcpStream
we may not need any support fromnative_tls
.The text was updated successfully, but these errors were encountered: