WebSocketProvider: this should not happen

[mentalrob]

Hi, i'm using quicknode's websocket endpoint for WebSocketProvider on BSC network. But while listening the pending transactions i got this this should not happen console output. What is this ? Why it prints something like this ?

[zemse]

Hey @mentalrob, are you still facing this problem? Can you provide any relevant code snippet?

[billy-the-ape]

I am seeing this consistently running this with node.js when I try to execute a transaction using swapExactETHForTokens on the router. It outputs this should not happen to the console 2-6 times before the transaction finally succeeds (sometimes it doesn't even return the tx response, but I can see the transaction is completed in bscscan)

Any suggestion for how to troubleshoot? My relevant code is mostly in this file:

https://github.com/wack-overflow/bsc-sniper/blob/main/util.ts#L101

[khanhquocnguyen]

I am seeing this consistently running this with node.js when I try to execute a transaction using swapExactETHForTokens on the router. It outputs this should not happen to the console 2-6 times before the transaction finally succeeds (sometimes it doesn't even return the tx response, but I can see the transaction is completed in bscscan)

Any suggestion for how to troubleshoot? My relevant code is mostly in this file:

https://github.com/wack-overflow/bsc-sniper/blob/main/util.ts#L101

That's exactly what I'm facing.
I tried to swapExactETHForTokens on the router, the transaction is completed successfully (check on bscscan) but tx.wait() was not resolved, and this should not happen is on the console.

[zemse]

Oh dang, that console log is because of this.

const oldOnMessage = provider._websocket.onmessage;
provider._websocket.onmessage = messageEvent => {
  console.log("websocket onmessage debug:", messageEvent.data) // to see data received
  oldOnMessage(messageEvent);
}

Can you mention the relevant message datas here?

[JR0210]

Also getting this issue, I've just switched from a single WebSocketProvider to multiple within a FallbackProvider. Any ideas? No onmessage debug console log from what I can see, just the "this should not happen"