A game is Ready after a 10-second check: watch its links and grade how they keep pace #94
Labels
No labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
cmoriarty/sports-breaker#94
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
A link is Ready after
verify(), which:That is about 10 seconds of evidence. After that, every 150 s, the re-check reads the manifest and 64 KB of a segment. Neither check asks whether the source keeps up with real time over minutes. A stream nobody could watch passes both, and the viewer is the first to find out.
Ole Miss vs. Georgia, 2026-11-07, about 7:50 pm ET. I polled the playing link's JSON playlist once a second for 63 s, from outside the app:
The idea
Watch the links the app would play, continuously and cheaply, and let readiness say how they have played.
upstream.fetch_concurrency): time it, check its bytes (media_shape) and count its frames (cadence).To settle in the design:
Done when
Built in PR #99 (merged as
732ab0a), deployed 2026-11-08 04:19Z (container 52cd495f611a); the OpenSpec change is archived in038f7a9. This stays open until it is seen working on a live followed game: a grade before the tune, a Warm background channel, and a Choppy stream that stays put.Live test, UTEP vs. Hawai'i, 2026-11-07 23:22–23:55 ET (first followed game after the deploy). Seen working: the kept link and both standbys were watched and graded on the readiness row and the channel: Unproven at first, then Steady after 2 minutes (givemestreams.cfd, pace 0.99, about 11 s of buffer), then Choppy (sportsframe.site, pace 0.83, about 34 s) and back to Steady (pace 1.0) as the source recovered. The game's grade followed its best kept stream.
Closed at the owner's word (2026-11-08): the fix is merged to develop in PR #99 (merge
732ab0a) and deployed. A new issue will be opened if a problem shows up.