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
caseNETWORK_ERROR_CODE_INVALID_STATE:
caseNETWORK_ERROR_CODE_NOT_IN_PROGRESS:
abort(); // If our internal state checks are working right, these errors should never show up.break;
Given that wasi-libc correctly follows the state diagram this behavior is the correct thing to do, IMO.
It's wasmtime that's at fault here. It (and every other engine) should either:
support connecting from a bound state (the preferred option of course), or:
return error-code::not-supported if it doesn't support connecting from a bound state.
pavelsavara
changed the title
__wasi_sockets_utils__map_error is missing conversion for NETWORK_ERROR_CODE_INVALID_STATE for connect wasi:socket
wasi-sockets: TCP connect from a Bound state.
Oct 24, 2024
__wasi_sockets_utils__map_error
is missing conversion forNETWORK_ERROR_CODE_INVALID_STATE
forconnect
inwasi:socket
Test case
TcpClientSocket_WhenBoundToWildcardAddress_LocalEPChangeToSpecificOnConnect
https://github.com/dotnet/runtime/blob/89f245e722eda87869dbb04690cb91361af8174c/src/libraries/System.Net.Sockets/tests/FunctionalTests/LocalEndPointTest.cs#L82-L103
Place to fix
wasi-libc/libc-bottom-half/sources/sockets_utils.c
Lines 20 to 22 in 7d4d3b8
Log
The text was updated successfully, but these errors were encountered: