Websocket Desync/Timeout results in losing writing progress about sysreptor HOT 2 CLOSED

Hi, thanks for reporting. We are already working on a fix because other users also encountered this problem.

The exception in the backend is quite easy to fix.

The frontend timeout is trickier. We could reliably reproduce the timeout by overwhelming the browser (e.g. typing very fast, holding backspace key). The browser is then busy and can no longer process websocket messages in time, thus exceeding the timeout. The root cause of the hang is that propagating text updates to reactive data structures is costly/slow. When there are many updates per second, the browser hangs. We try to improve the performance of update event handling (maybe throtteling and applying them in batches works better).

from sysreptor.

Fixed in https://github.com/Syslifters/sysreptor/releases/tag/2024.43

from sysreptor.