-
Notifications
You must be signed in to change notification settings - Fork 62
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
wasi-sockets: New SO_REUSEADDR test #322
Comments
Thanks for the heads-up 👍 |
Thanks for the clarification here. I was wondering @badeend if you had any ideas why we need to separately track the global address registrations for the |
I managed to trace the issue with the global address registration down to a Node.js low-level bindgen calling convention, with a weird workaround, where Node.js needs to call |
Just a heads up; I've clarified in the WITs that SO_REUSEADDR should be set on TCP sockets by default when performing an explicit
bind
. I've added a new test for it over in the wasmtime repo: bytecodealliance/wasmtime#7690I don't think this requires any additional work in JCO, because libuv appears to already do this for you.
The text was updated successfully, but these errors were encountered: