You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
fix: terminate closing connections earlier if normal close responses fail
6
+
7
+
If Slack doesn't respond to a close frame, the WebSocket connection is now force-terminated instead of waiting for a response that won't arrive. Since [disconnects are expected](https://docs.slack.dev/apis/events-api/using-socket-mode/#disconnect) every few hours, this avoids repeated "pong wasn't received" warnings and speeds up reconnection.
// The force-terminate should produce 1 close event per reconnection attempt
448
+
assert.strictEqual(closeCount,1);
449
+
awaitclient.disconnect();
450
+
});
408
451
it('should reconnect if server does not respond with `pong` message within specified client ping timeout after initially responding with `pong`',async()=>{
409
452
wss.close();
410
453
// override the web socket server so that it DOESNT auto-respond to ping messages with a pong, except for the first time
0 commit comments