A swap or recovery lands on a stream that just failed, through another site #91
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#91
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
When a link fails, the app cools that one player page (
Ladder.fail, for 10 min). It doesn't remember which stream failed. Other sites that carry the same stream stay eligible as the standby, as the second standby and on the ladder. So a swap or a recovery can land straight back on a stream that just failed, through a different site.Ravens vs. Jaguars, 2026-11-05 (the swaps are listed in #90). Behind 9 sites there were 4 streams, A to D. Matching each stream's own clock in the splice lines showed which site carried which:
Four of the 11 swaps landed on a stream that had failed in the last six minutes, or on the stream being left. Together those four played about 5 minutes. The rest of the time between them was spent on filler and further swaps.
Where in the code:
resolution.invalidatecools the failed player page, not its stream.verify_standby'savoidholds only the streams kept right now (the link playing, the standby, the second standby), not the streams that just failed._standby_gonemoves the second standby up without checking it against the new main link. A copy of the second standby becomes a copy of the stream now playing.Channel._maybe_swapcompares scores only. A same-stream standby always scores "healthy" against a degrading main link, so it wins.What it costs
A swap to the same stream, or to one that just failed, rarely helps. The viewer gets another splice, often filler, and the channel spends its standby. After that, the recovery falls to the ladder or a re-read. On a night with only a few streams to choose from, this is what the "rotating through the same streams" looks like.
The idea
stream_identity.identity) and the time. For the cooldown, every link of that stream counts as cooling:avoid;Defaults:
cooldown_seconds, 10 min).For the design to check: whether the URL identity alone caught tonight's repeats. All of A's sites may not have used the same CDN URL. The source's own clock (the first segment's timestamp, which the verify probe already reads) could be a second signal: two links whose clocks agree to within a few seconds are the same stream.
Not part of this: showing the swaps on the card. That is #90, and with it this rule's skips can be seen.
Related: #74 (a different stream for the standby), #64 (the second standby), #65 (a relapse to the standby).
Ole Miss vs. Georgia, 2026-11-07: every swap landed on the same stream
The channel was tuned at 7:41 pm ET. Between 7:42 and 7:58 it made 12 degrading swaps and 3 recoveries across 10 sites: s2watch.cyou, powerstream.club, givemestreams.cfd, iptvcast.lol, fast-streams.biz, nfl-castnow.lat, sportsframe.site, bally-sports.lat, tvsportslive.fr and watchsports.online. All of them carried one stream. The splice lines' raw clock runs straight through every swap, from 10188 s to 11280 s.
That stream was the problem: it published about 0.8× real time (#94). No swap could have helped, and each one cost a splice and usually filler:
skipped_seconds: 0.Added to this issue (milestone "Ready means watched")
stream_id. Tonight's wase84dab19….verify()already downloads the newest segment, so the timestamp costs nothing extra.Not confirmed: whether tonight's sites resolved to one playlist file name. The URL is in neither the INFO log nor the events. So it is open whether #74's rule matched them and the standby fell back to a copy, or whether the rule missed them.
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 standby (powerstream.club, later tvsportslive.fr) was recognised as a copy of the playing stream, and at 23:29:55 the degrading channel refused it ("the same stream as the one playing; staying").
Not working: when the stream then failed outright (a 503 on givemestreams.cfd's playlist), recovery landed on the copy first, which failed 3 s later. Filed as #101.
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.