sc-rpc still on futures 1.x

[Voxelot]

Please upgrade sc-rpc to the latest version of https://github.com/paritytech/jsonrpc 17.0.0.

Currently all the exported generated rpc clients in sc-rpc are still on futures 1.x. It looks like upgrading to jsonrpc 17.0.0 will fix this.

[Voxelot]

sc-rpc-api also should be updated https://github.com/paritytech/substrate/blob/v3.0.0/client/rpc-api/Cargo.toml#L19

[kianenigma]

cc @tomusdrw

I faced issues with this myself and having to deal with two versions of tokio runtime within one codebase was a bit of a hassle.

[tomusdrw]

It's a known issue and we are working on fixing this. AFAIK the solution that we've settled on is jsonrpsee integration. CC @dvdplm @gnunicorn.

[Voxelot]

jsonrpsee integration makes sense, are there any issues I could follow to be notified of when the migration is complete? #3099 hasn't seen an update for over a year :/

Depending on how far out that is, would it be less of a hassle in the near term to just bump the versions to jsonrpc 17.0.0 as it is already on tokio 0.2? Then I could go back to using #[tokio::test] and #[tokio::main] instead of tokio_compat :D

[dvdplm]

The work to migrate substrate off jsonrpc and switch to jsonrpsee happens here and work is under way. The client is further along than the server though and substrate-integration is at the PoC-level still. It's looking good though and we expect fairly rapid progress on this over the coming months.

I believe @gnunicorn made an attempt to upgrade to jsonrpc v17 as a stop-gap solution for the painful tokio situation but found it to be less than trivial.

[Voxelot]

Really appreciate all the info. I'm going to close this issue for now since it's not really actionable until the re-write of jsonrpc is complete.