You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
On Linux, communicating with IPv4 hosts using an IPv6 socket will typically Just Work. However, on Windows it will produce a mysterious WSAEFAULT error unless IPV6_V6ONLY is explicitly turned off in advance. Linux can also be configured to default that option on, and OpenBSD does not permit it to be turned off at all.
Should tokio (or mio) make an effort to provide clearer error messages and/or a consistent default behavior in this circumstance?
The text was updated successfully, but these errors were encountered:
I would say yes for the TcpStream types that are provided as they are intended to be friendly / portable. This seems like a similar problem that std TcpStream would have as well?
I'm thinking of rust-lang/rust#34440 (which I've now dug up). The conclusion there was that libstd didn't change, which to me means that we probably don't want to change tokio-core
On Linux, communicating with IPv4 hosts using an IPv6 socket will typically Just Work. However, on Windows it will produce a mysterious
WSAEFAULT
error unlessIPV6_V6ONLY
is explicitly turned off in advance. Linux can also be configured to default that option on, and OpenBSD does not permit it to be turned off at all.Should tokio (or mio) make an effort to provide clearer error messages and/or a consistent default behavior in this circumstance?
The text was updated successfully, but these errors were encountered: