Stream reliability

Stream reliability, planned 2026-10-31 from Chelsea vs. Man Utd. One branch, one merge to develop, one deploy when no one is mid-game.

Order:

  1. #65: a recovery takes the ready standby rather than re-reading a link that already failed in the last 5 min.
  2. #63: the stream check downloads as many segments at once as the channel will (three), and judges pace on that when the source allows it.
  3. #64: a second standby for played games, and per-game demotion of links that keep finding nothing.
  4. #66: look on live games at why hosts find no stream, and fix the reader for what it misses. It runs alongside the others, while games are live.

Decisions are in the issue comments.

No due date
100% Completed
Stream reliability: relapse to the standby, a parallel pace check, a second standby, and the reader's misses
All checks were successful
ci / Unit tests, type check, bundle (pull_request) Successful in 45s
ci / One container, e2e click-to-play inside the image (pull_request) Successful in 1m30s
#67 by cmoriarty was merged 2026-10-31 13:42:26 -04:00
#66 by cmoriarty was closed 2026-10-31 13:45:52 -04:00