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
Devices/Simulators/Machine affected: Desktop Linux
Reproducible in the testnet? (Yes/No): yes
Related issues: #
Bug report
Expected behavior
Browser light clients can establish and hold connections with peers.
Actual behavior
Browser clients panic when connecting to the first peer (seed) with:
thread '<unnamed>' panicked at 'there is no reactor running, must be called from the context of a Tokio 1.x runtime': /core-rs-albatross/network-interface/src/request/mod.rs:223
and can then no longer maintain connections, as peers disconnect after a few seconds because of response timeouts on their side.
Compile the browser client locally (./web-client/scripts/build.sh --only web --skip-types --skip-wasm-opt) and serve the web-client folder, then go to http://localhost/example. If seed1 is not up, change the seed node in web-client/example/module.js to a node that is up.
The text was updated successfully, but these errors were encountered:
General information
Bug report
Expected behavior
Browser light clients can establish and hold connections with peers.
Actual behavior
Browser clients panic when connecting to the first peer (seed) with:
and can then no longer maintain connections, as peers disconnect after a few seconds because of response timeouts on their side.
Steps to reproduce
Either
or
./web-client/scripts/build.sh --only web --skip-types --skip-wasm-opt
) and serve theweb-client
folder, then go to http://localhost/example. Ifseed1
is not up, change the seed node inweb-client/example/module.js
to a node that is up.The text was updated successfully, but these errors were encountered: