-
Notifications
You must be signed in to change notification settings - Fork 226
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
Windows sockets not waking in certain conditions #274
Comments
+1 I'm also seeing this issue on windows, and it's a hard block on doing any proper networking since it makes it highly unreliable. |
I'm seeing this issue as well when trying to run a server I wrote using monoio on Windows |
Windows support is still at early stage. @Lzzzzzt Do you have any idea about this issue? |
Currently, I know almost nothing about Windows Socket, maybe I will investigate it after finishing my current work. |
Appreciate the attention to the issue, if there's anymore that can be provided to help/test just let me know. |
Version
List the versions of all
monoio
crates you are using. The easiest way to getthis information is using
cargo tree
subcommand:monoio v0.2.3
Platform
Windows 11 Pro 10.0.22631 Build 22631
Description
Enter your issue details here.
One way to structure the description:
When reading from a TCP socket using
read
, sometimes it just does not wake even though the socket has pending data.I tried this code:
I expected to see this happen: All of the contents of the
TEXT
array to be sent over the socket and echoed backInstead, this happened: The waker was never called even though there was data in the socket.
The text was updated successfully, but these errors were encountered: