Braid's clock cannot hold server-driven state #415
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
What happens. run 181's deal animation lives in a 1.6 s dealing phase the Colyseus server advances; the page re-rendered before any separate screenshot, so no filmstrip.
Fix. while the clock is paused, queue incoming WebSocket
messageevents (and fetch responses) and release them on resume.Done when. the clock journey holds a page whose state a mock socket pushes 500 ms after the freeze.
From run 181, the verifying run after #407; the log is
docs/design/measurements/work/run-180/findings.md.Shipped in PR #421 (
ff9381d8), changejudge-round-two-mechanics. Braid's clock now gates what a server pushes: while paused, a WebSocket or EventSourcemessageand afetchresponse are held, stamped with their arrival, and delivered in order when the clock steps past it or resumes;open,closeanderrorpass. Journey inui/e2e/judge-probes.spec.ts: a page paused at 150 ms whose socket pushes 500 ms later does not re-render until the clock is stepped past it, and an unpaused page sees the message at once.