fix(node-wasm): workaround to clean extra message from worker

node-wasm/src/client.rs

@@ -58,6 +58,7 @@ impl NodeClient {
 
         let worker = WorkerClient::new(port)?;
 
+        // todo: refactor when oneshots are implemented
         // keep pinging worker until it responds.
         // NOTE: there is a possibility that worker can take longer than a timeout
         // to send his response. Client will then send another ping and read previous
@@ -71,6 +72,9 @@ impl NodeClient {
                 break;
             }
         }
+        // wait another timeout to read potential extra response from worker that
+        // could be caused by the loop above
+        let _ = timeout(200, worker.recv()).await;
 
         debug!("Connected to worker");
 

node-wasm/src/ports.rs

@@ -219,6 +219,18 @@ impl WorkerClient {
 
         Ok(worker_response)
     }
+
+    // todo: remove when oneshots are implemented, used in workaround for initial worker connection
+    pub(crate) async fn recv(&self) -> Result<WorkerResponse> {
+        let mut response_channel = self.response_channel.lock().await;
+        let worker_response = response_channel
+            .recv()
+            .await
+            .expect("response channel should never drop")
+            .context("error receiving command")?;
+
+        Ok(worker_response)
+    }
 }
 
 impl Drop for WorkerClient {