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
Merge pull request #2872 from c3d1c06c-bf26-477e-b0eb-c50ef4477ba6/master
The Problem:
The current code creates a new WebSocket connection in the reconnection callback but stores it in a local variable (newWs), leaving the global ws variable pointing to the closed connection.
This causes the polling fallback to continue running even after a successful WebSocket reconnection, resulting in duplicate metric updates.
The Solution:
By directly assigning to the global ws variable, the fix ensures that:
- The polling check at line 367 (if (!ws || ws.readyState !== WebSocket.OPEN)) works correctly
- Only one update mechanism (WebSocket or polling) runs at a time
- The dashboard doesn't receive duplicate updates.
0 commit comments