Braid's clock cannot hold server-driven state #415

Closed
opened 2026-11-08 00:04:10 -05:00 by cmoriarty · 1 comment
Owner

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 message events (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.

**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 `message` events (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`.
Author
Owner

Shipped in PR #421 (ff9381d8), change judge-round-two-mechanics. Braid's clock now gates what a server pushes: while paused, a WebSocket or EventSource message and a fetch response are held, stamped with their arrival, and delivered in order when the clock steps past it or resumes; open, close and error pass. Journey in ui/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.

**Shipped in PR #421 (ff9381d8), change `judge-round-two-mechanics`.** Braid's clock now gates what a server pushes: while paused, a WebSocket or EventSource `message` and a `fetch` response are held, stamped with their arrival, and delivered in order when the clock steps past it or resumes; `open`, `close` and `error` pass. Journey in `ui/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.
Sign in to join this conversation.
No labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
cmoriarty/braid#415
No description provided.