fix(ping/rust): Implemented 0.50 changes

[umgefahren]

As requested by @thomaseizinger, this changes the test plans to take the removed APIs into account. See libp2p/rust-libp2p#3170 for details.

[thomaseizinger]

Thanks!

[thomaseizinger]

@mxinden I can't merge this myself, please have a look!

[mxinden]

Thanks for the patch @umgefahren!

[umgefahren]

19a8de2 is not correct. Since it's called in an async_std block Tokio is the wrong executor and might lead to a runtime panic if I'm correct. In other words: If Tokio is correct, we should also use Tokio::main

[mxinden]

19a8de2 is not correct. Since it's called in an async_std block Tokio is the wrong executor and might lead to a runtime panic if I'm correct. In other words: If Tokio is correct, we should also use Tokio::main

You are absolutely right @umgefahren. My bad. Sorry for pushing a wrong commit to your branch.

Regarding the previous CI failure, my best next guess is that the commit hash referenced in the Cargo.toml is too old.

test-plans/ping/rust/Cargo.toml

Line 34 in 31a1288

rev = "368705a1465c4322948d14ee46d42475c472ca1e" # This should usually point to a commit on master.

Would you mind reverting my commit and updating the commit hash to a recent commit on master, ideally the one of v0.50.0 tag?

[mxinden]

I don't think moving to tag would work here, given that we use sed in our Dockerfile matching on the string rev.

I might have been not very clear. Sorry. Let's use the commit hash that v0.50.0 points at.

[umgefahren]

Oh I see

[thomaseizinger]

Now that we have released v0.50.0 we should actually add that as a release and have this point to the most recent hash on master here!

[umgefahren]

Should this be part of this PR?

[thomaseizinger]

It doesn't have to be. I think we can merge this separately :)

[thomaseizinger]

I opened #87 and also fixed the deprecation warnings there.

[mxinden]

Closing here in favor of #87. Thanks for the help!