Repos:
Transport: ws, Secure: noise, Muxer: mplex
Summary
chromium-rust-v0.53 (WASM build running in Chromium) times out when dialing python-v0.x as listener via ws/noise/mplex. The python listener starts and publishes its multiaddr, but the WASM dialer never successfully connects. The test hits the 180-second timeout.
Failing tests (1)
chromium-rust-v0.53 x python-v0.x (ws, noise, mplex)
Error output
Test timed out after 180s
Notes
This may be a WASM WebSocket transport incompatibility with the Python implementation. The chromium-rust-v0.53 WASM dialer successfully connects to other implementations (go, rust, js) via ws, so the issue is specific to the python listener. Possible causes include differences in WebSocket subprotocol negotiation or noise handshake timing in the WASM environment.
Repos:
b7914e407da34c99fb76dcc300b3d44b9af97fac)22ea173ac0359a386275bdf6b846bc52a0082e91)Transport: ws, Secure: noise, Muxer: mplex
Summary
chromium-rust-v0.53 (WASM build running in Chromium) times out when dialing python-v0.x as listener via ws/noise/mplex. The python listener starts and publishes its multiaddr, but the WASM dialer never successfully connects. The test hits the 180-second timeout.
Failing tests (1)
chromium-rust-v0.53 x python-v0.x (ws, noise, mplex)Error output
Notes
This may be a WASM WebSocket transport incompatibility with the Python implementation. The chromium-rust-v0.53 WASM dialer successfully connects to other implementations (go, rust, js) via ws, so the issue is specific to the python listener. Possible causes include differences in WebSocket subprotocol negotiation or noise handshake timing in the WASM environment.