I've run into a strange issue where a connection is frequently ended and restarted on the server, via the "disconnect" event. I have no idea specifically what is emitting the "disconnect", but it occurs at fairly regular intervals, leading me to believe it has to do with the heartbeat timeout. I'm planning to go source diving later, but first wanted to check and see if this was a documented issue. I've also included the info and debug statements.
debug - served static content /socket.io.js
debug - client authorized
info - handshake authorized 1636308112793994798
debug - set heartbeat interval for client 1636308112793994798
debug - client authorized for
debug - websocket writing 1::
debug - emitting heartbeat for client 1636308112793994798
debug - websocket writing 2::
debug - set heartbeat timeout for client 1636308112793994798
debug - websocket received data packet 2::
debug - got heartbeat packet
debug - cleared heartbeat timeout for client 1636308112793994798
debug - set heartbeat interval for client 1636308112793994798
debug - emitting heartbeat for client 1636308112793994798
debug - websocket writing 2::
debug - set heartbeat timeout for client 1636308112793994798
debug - websocket received data packet 2::
debug - got heartbeat packet
debug - cleared heartbeat timeout for client 1636308112793994798
debug - set heartbeat interval for client 1636308112793994798
info - transport end
debug - set close timeout for client 1636308112793994798
debug - cleared close timeout for client 1636308112793994798
debug - cleared heartbeat interval for client 1636308112793994798
Client disconnect // ( Emitted by my own disconnect listener )
debug - discarding transport
debug - client authorized
info - handshake authorized 11622896942027911398
// etc...