Open caver456 opened 3 years ago
other recent code changes involved avoiding multiple back-to-back websockets sends, to avoid race conditions and html flickers on listeners, by only pushing once per compound operation like new pairing, and pairing status change to DONE. Hopefully that's the cause; but, the server appears dead from that point on.
sometimes the websockets server just stops sending updates. Not sure if this is because it has stopped listening, or because the server has stopped sending. Observed while walking a pairing through its statuses. Most recent code changes were to the handler for setting pairing status to 'DONE'. Local database and localhost database seem to be getting appropriate edits - it seems to just be a dead websocket server.
Noticed this sequence in the websocket log around that time, but only for one of the occurances of dropped connections:
Maybe this would be simplified if the server kept its ws connection open while running, rather than open and close with every message?