Switch from wasm-timer to fluvio-wasm-timer...

... which addresses the problem from Amanieu/parking_lot#269
by taking the unmerged workaround of tomaka/wasm-timer#13 ,
as wasm-timer appears to be unmaintained.

Author: neacsu

Cargo.lock

@@ -41,8 +41,8 @@ version = "0.4"
 path = "../../wasm-utils"
 
 # only import it in wasm. Prefer proper tokio timer in non-wasm
-[target."cfg(target_arch = \"wasm32\")".dependencies.wasm-timer]
-version = "0.2"
+[target."cfg(target_arch = \"wasm32\")".dependencies.fluvio-wasm-timer]
+version = "0.2.5"
 
 # this is due to tungstenite using `rand` 0.8 and associated changes in `getrandom` crate
 # which now does not support wasm32-unknown-unknown target by default.

common/client-libs/gateway-client/Cargo.toml

@@ -26,7 +26,7 @@ use tungstenite::protocol::Message;
 use tokio_tungstenite::connect_async;
 
 #[cfg(target_arch = "wasm32")]
-use wasm_timer;
+use fluvio_wasm_timer as wasm_timer;
 #[cfg(target_arch = "wasm32")]
 use wasm_utils::websocket::JSWebsocket;
 

common/client-libs/gateway-client/src/client.rs

@@ -16,7 +16,7 @@ reqwest = { version="0.11", features=["json"] }
 thiserror = "1"
 log = "0.4"
 url = "2"
-wasm-timer = "0.2"
+fluvio-wasm-timer = "0.2.5"
 
 # required for nymd-client
 # at some point it might be possible to make it wasm-compatible

common/client-libs/validator-client/Cargo.toml

@@ -141,7 +141,7 @@ impl Client {
                 error!("{}", url)
             }
             // Went with only wasm_timer so we can avoid features on the lib, and pulling in tokio
-            wasm_timer::Delay::new(Duration::from_secs(sleep_secs)).await?;
+            fluvio_wasm_timer::Delay::new(Duration::from_secs(sleep_secs)).await?;
         }
     }