[Heartbeat question] is a ping/pong cycle skipped if a 'standard' message is received on the websocket?

[1nfm1k3]

I configured a websocket with a pretty standard heartbeat configuration:

heartbeat: {
      message: 'ping',
      returnMessage: 'pong',
      interval: 10000,
      timeout: 60000
    }

However, I noticed that no ping/pong exchanges were happening in my use case. So, I lowered down the interval to something like 1000, and at that point I could see the ping/pong messages being sent.

Finally, I realized the backend sends a message on this websocket roughly every ~5 seconds. Is this what is preventing the ping messages from being sent by the client? Or, more generally: receiving a 'standard' message on the websocket clears up a ping/pong cycle or am I misunderstanding something?

Using ^4.13.0.

[briancoit]

It seems this is a bug introduced after 4.9.0 - pings appear to be suppressed by received messages.

[1nfm1k3]

From my experience with the ping/pong feature, I suppose there may be some issues related to dirty timestamps also with reconnections (the ones happening with shouldReconnect, reconnectAttempts, reconnectInterval options, and also with switching the connect hook parameter) - sometimes, I've observed ping/pongs not being sent in the reconnected subsequent websockets.

I'm sorry not being able to provide a reproducible example or codebox, since for the time being I implemented a custom ping-pong hook on top of the existing websocket.