Test jsonrpsee v0.20

[haerdib]

Test PR for #692

[niklasad1]

You can't use block_on on tokio multi-thread it will panic.

The best would would be to change this to:

#[maybe_async::sync_impl]
impl Request for JsonrpseeClient {
	fn request<serde_json::Value>(&self, method: &str, params: RpcParams) -> Result<R> {
                let (tx, rx) = tokio::sync::oneshot();
 
                tokio::spawn(async move {
                    let res = self.inner.request(method, RpcParamsWrapper(params))).await.map_err(|e| Error::Client(Box::new(e)));
                    tx.send(res);
                });

                let rx = rx.blocking_recv().unwrap();
		let deserialized_value: R = serde_json::from_value(rx)?;
		Ok(deserialized_value)
	}
}

Otherwise, you need to create a single threaded tokio-runtime https://docs.rs/tokio/latest/tokio/runtime/struct.Builder.html#method.new_current_thread

[haerdib]

The problem with the solution you're providing is, that it enforces the creation of a tokio task / thread outside of the request function, therefore breaking our current sync-api. With the current examples, it runs into the following runtime error at the blocking_recv() part:

ERROR: Cannot block the current thread from within a runtime.
This happens because a function attempted to block the current thread while the thread is being used to drive asynchronous tasks.

I'm not entirely sure what we should do here - either provide an all-inclusive function with a handle try_current matching to whatever the user does outside, or enforce either tokio or non-tokio threading.

In the long run, probably the best thing would be to either remove sync-api altogether on our side or introduce a sync-api for jsonrspee without tokio enforcement.

[niklasad1]

ok, I see sorry for giving a bad suggestion. That was news to me

[haerdib]

Not a bad suggestion at all - it really helped me along the way. Thank you very much!

[haerdib]

closing this as obsolete - we removed the sync api as of #699