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
I am having this weird error a due the use of tokio out of context for the "WsTransportClientBuilder".
thread 'main' panicked at /.cargo/git/checkouts/jsonrpsee-b50257996090af44/658afa5/client/transport/src/ws/mod.rs:480:19:
there is no reactor running, must be called from the context of a Tokio 1.x runtime
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
Yes, jsonrpsee is tightly-coupled to tokio and requires the tokio runtime to be initialized because it's using tokio::spawn under the hood to spawn the background task.
Can't use tokio on your platform or what's the reason to use async-io crate?
when you work in embedded systems "every little byte helps". Tokio is a very good crate but is too fat when compared with async-io.
For instance for this case above(STD/ESP-IDF framework) we would need to use OpenThread with unsafe code instructions like "esp_vfs_eventfd_register()". And we would need to reorganize the partition-tables in order to work with Tokio.
Cheers,
niklasad1
changed the title
there is no reactor running, must be called from the context of a Tokio 1.x runtime-[xtensa-esp32s3-espidf]
client: support other async runtimes than tokioApr 2, 2024
Hello,
I am having this weird error a due the use of tokio out of context for the "WsTransportClientBuilder".
Is this because of the async_io ?
cargo.toml
The text was updated successfully, but these errors were encountered: