fix(display): retry every failed request with backoff, and never give up

Conversation 1 Commits 3 Files Changed 5

+489 -41

3 Commits

Author	SHA1	Message	Date
ekklesiaandClaude Opus 5.5	bf4e98fa30	ci: run session-blip and stream-failure on every change CI / lint (pull_request) Successful in 12s Details CI / typecheck (pull_request) Successful in 14s Details CI / test (pull_request) Successful in 22s Details CI / build (pull_request) Successful in 18s Details CI / integration (pull_request) Successful in 3m40s Details Both failed on main before this PR: a display that failed its first viewer-session request, or its first realtime connection, never recovered without a reload. With the retries in place they pass, and CI now holds them there. Co-Authored-By: Claude Opus 5.5 <[email protected]>	2026-10-05 21:32:03 -05:00
ekklesiaandClaude Opus 5.5	fbc8af7510	fix(display): retry every failed request with backoff, and never give up A display tried each of its network paths once: - A registration that failed left it continuing from its persisted state, behind the offline banner, with no realtime, heartbeat or retry, until someone reloaded it. This is what the production kiosk showed after a restart. - A failed state refresh scheduled no further refresh, so a display whose realtime was also down never fetched state again. - A realtime stream the host reported closed was never subscribed again. Each path now retries on its own backoff: about 1 s, doubling to a one-minute ceiling, with jitter so a building's screens do not return in lockstep. There is no attempt limit, because a television has nobody to press Retry. Each resets when its request works again. - Registration retries until it works, then brings the display live exactly as a first-time success does. - A failed refresh schedules its own retry, with no realtime needed. - A closed realtime subscription is replaced. - Stopping clears every retry. The recovery test's virtual window shrinks from an hour to five minutes: eight failures back off for at most about 183 s, and an hour of offline-continuation timers made the test slow without proving more. Co-Authored-By: Claude Opus 5.5 <[email protected]>	2026-10-05 21:31:55 -05:00
ekklesiaandClaude Opus 5.5	518fd101a2	test(display): a display recovers from every failed request without a reload Pins what a kiosk needs from each network path, on a virtual clock: a registration that fails once is retried with backoff until it works, a state refresh that fails is retried without a realtime nudge, and a realtime stream the host reports closed is subscribed again. Nothing is scheduled after stop. Fails today on all three paths: each is tried once. The first matches the production screen exactly: mounted, showing "Offline — continuing from the last update", with no heartbeat and no retry until someone reloads it. Co-Authored-By: Claude Opus 5.5 <[email protected]>	2026-10-05 21:31:49 -05:00

Author

SHA1

Message

Date

ekklesiaandClaude Opus 5.5

bf4e98fa30

ci: run session-blip and stream-failure on every change

CI / lint (pull_request) Successful in 12s

Details

CI / typecheck (pull_request) Successful in 14s

Details

CI / test (pull_request) Successful in 22s

Details

CI / build (pull_request) Successful in 18s

Details

CI / integration (pull_request) Successful in 3m40s

Details

Both failed on main before this PR: a display that failed its first
viewer-session request, or its first realtime connection, never
recovered without a reload. With the retries in place they pass, and
CI now holds them there.

Co-Authored-By: Claude Opus 5.5 <[email protected]>

2026-10-05 21:32:03 -05:00

ekklesiaandClaude Opus 5.5

fbc8af7510

fix(display): retry every failed request with backoff, and never give up

A display tried each of its network paths once:
- A registration that failed left it continuing from its persisted
  state, behind the offline banner, with no realtime, heartbeat or
  retry, until someone reloaded it. This is what the production kiosk
  showed after a restart.
- A failed state refresh scheduled no further refresh, so a display
  whose realtime was also down never fetched state again.
- A realtime stream the host reported closed was never subscribed
  again.

Each path now retries on its own backoff: about 1 s, doubling to a
one-minute ceiling, with jitter so a building's screens do not return
in lockstep. There is no attempt limit, because a television has
nobody to press Retry. Each resets when its request works again.
- Registration retries until it works, then brings the display live
  exactly as a first-time success does.
- A failed refresh schedules its own retry, with no realtime needed.
- A closed realtime subscription is replaced.
- Stopping clears every retry.

The recovery test's virtual window shrinks from an hour to five
minutes: eight failures back off for at most about 183 s, and an hour
of offline-continuation timers made the test slow without proving more.

Co-Authored-By: Claude Opus 5.5 <[email protected]>

2026-10-05 21:31:55 -05:00

ekklesiaandClaude Opus 5.5

518fd101a2

test(display): a display recovers from every failed request without a reload

Pins what a kiosk needs from each network path, on a virtual clock: a
registration that fails once is retried with backoff until it works, a
state refresh that fails is retried without a realtime nudge, and a
realtime stream the host reports closed is subscribed again. Nothing is
scheduled after stop.

Fails today on all three paths: each is tried once. The first matches
the production screen exactly: mounted, showing "Offline — continuing
from the last update", with no heartbeat and no retry until someone
reloads it.

Co-Authored-By: Claude Opus 5.5 <[email protected]>

2026-10-05 21:31:49 -05:00

fix(display): retry every failed request with backoff, and never give up #5