relay: panics due to unimplemented time in wasm

[dariusc93]

Summary

libp2p panics in the browser with time not implemented on this platform due to unsupported time module when attempting to listen to a relay, despite enabling instant/wasm-bindgen feature explicitly in libp2p-relay module. Is it not really clear where std::time::Instant (or std::time::SystemTime) is being exposed when targeting was32-unknown-unknown.

Expected behavior

Not to panic when attempting to listen to relay

Actual behavior

Panics with time not implemented on this platform despite wasm feature being explicitly enabled

Relevant log output

No response

Possible Solution

No response

Version

0.53.2 and github at 042174e

Would you like to work on fixing this bug ?

Maybe

[dariusc93]

Doing a quick scan over the code, i did notice the following using std instead of the instant crate for SystemTime, although this is for the HOP protocol, so this may not be relevant but still good-to-know

rust-libp2p/protocols/relay/src/protocol/outbound_hop.rs

Line 22 in bee8199

use std::time::{Duration, SystemTime};

rust-libp2p/protocols/relay/src/protocol/inbound_hop.rs

Line 21 in bee8199

use std::time::{Duration, SystemTime};

[dariusc93]

From testing, it looks like it is related to what is used in *_hop though I thought HOP protocol was related to the relay server. I may have it backwards in that case.