Admin: the Playing card's wait strip keeps one scale, with a y-axis #114
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#114
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?
On the Playing card (#105), the strip of the source's waits for a new segment has no fixed scale and no y-axis. The owner likes the live view but called the moving proportions a bug.
What happens
waitBarsandlateLineinfrontend/src/admin.ts).The idea
Health.classifyandfailed_byinbackend/app/channel.pycall the upstream failed at 2× the target duration, but the strip's waits are timed from the playlist listing (_waits).Done when
waitBarsandlateLineput the line at the same height whether the longest wait is 2 s or 30 s;late_after_seconds4, the strip shows the axis labels 0, 4 s and 8 s.Seen live at 15:37Z on the same channel, after filing: the line is the failure threshold some of the time.
powerstream.club (hls.lshls.st) failed: no new segment for 4 s, and 3 s later the channel recovered on the standby (bally-sports.lat).So the strip's waits (timed from the playlist listing,
_waits) and the failure check (now - last_new_segment_atat the health check) measure differently. The fix should make the strip and its help text agree with the check that actually fails the stream.Closing: merged to develop in PR #119 (merge
73f86a3), milestone 39. It deploys once nobody is watching.What changed:
Not seen live yet.
Deployed 2026-11-08 17:27:26Z: commit
73f86a3, container a07efdae03b6, 36.6 s down, no errors in the log.