A background channel that fails with no standby drops and cools the game's only link #137

Closed
opened 2026-11-09 23:45:02 -05:00 by cmoriarty · 1 comment
Owner

When a kept-warm channel fails and no standby is ready, the channel closes, the entry is dropped and its link cools for ten minutes (CHANNEL_COOLDOWN_SECONDS). If that link was the game's only working one, the next checks try only the links that cannot be read, and the game shows Checking or Failing until the cooldown ends.

Seen 2026-11-09 evening
Thetvapp streams failed in the channel within 20 to 90 s (fixed in PR #132). Each failure took the game out of Ready, and the checks that followed spent 60 to 210 s each on dead hub links. Indiana vs. Syracuse went round this three times in 45 minutes, Miami vs. North Florida and Hornets vs. Cavaliers twice each. The stream failures were the cause; this rule is what turned them into a list of games stuck Checking.

The same happens to a re-check failure (noted in PR #131): a failed re-check cools the only link, and a viewer's click then takes the cooled link anyway.

Decision needed
What should a game with one working link do when that link fails once with nobody watching?

  1. Keep the link without cooling it and re-read it at once (a watched channel's recovery already re-reads the same link first).
  2. Cool it for much less time when the ladder has no other usable link.
  3. Leave it: a flaky source should not hold Ready.

Done when a single failure of a game's only working link, with nobody watching, no longer leaves the game not Ready for ten minutes.

When a kept-warm channel fails and no standby is ready, the channel closes, the entry is dropped and its link cools for ten minutes (`CHANNEL_COOLDOWN_SECONDS`). If that link was the game's only working one, the next checks try only the links that cannot be read, and the game shows Checking or Failing until the cooldown ends. **Seen 2026-11-09 evening** Thetvapp streams failed in the channel within 20 to 90 s (fixed in PR #132). Each failure took the game out of Ready, and the checks that followed spent 60 to 210 s each on dead hub links. Indiana vs. Syracuse went round this three times in 45 minutes, Miami vs. North Florida and Hornets vs. Cavaliers twice each. The stream failures were the cause; this rule is what turned them into a list of games stuck Checking. The same happens to a re-check failure (noted in PR #131): a failed re-check cools the only link, and a viewer's click then takes the cooled link anyway. **Decision needed** What should a game with one working link do when that link fails once with nobody watching? 1. Keep the link without cooling it and re-read it at once (a watched channel's recovery already re-reads the same link first). 2. Cool it for much less time when the ladder has no other usable link. 3. Leave it: a flaky source should not hold Ready. **Done when** a single failure of a game's only working link, with nobody watching, no longer leaves the game not Ready for ten minutes.
Author
Owner

Fixed, by a decision Claude took while the owner slept; reverse it if you disagree.

A link that had verified for the game now cools for 60 s, not ten minutes, while no other link that has verified for it can be read. Each further failure within half an hour doubles the wait: 2, 4, 8 minutes, then the ordinary ten. A link that never verified keeps the ten minutes, and so does a proven link while another proven one can be read. It covers both a failed channel and a failed re-check.

Not kept across a restart: after one, every link cools the full time until it verifies again.

Merged in PR #140 (25fa577), deployed 2026-11-10 05:21Z, archived in 4952376. No followed game was live at the deploy, so none of it has been seen in production yet. Reopen if a game with one working link still sits not Ready for ten minutes.

Fixed, by a decision Claude took while the owner slept; reverse it if you disagree. A link that had verified for the game now cools for 60 s, not ten minutes, while no other link that has verified for it can be read. Each further failure within half an hour doubles the wait: 2, 4, 8 minutes, then the ordinary ten. A link that never verified keeps the ten minutes, and so does a proven link while another proven one can be read. It covers both a failed channel and a failed re-check. Not kept across a restart: after one, every link cools the full time until it verifies again. Merged in PR #140 (25fa577), deployed 2026-11-10 05:21Z, archived in 4952376. No followed game was live at the deploy, so none of it has been seen in production yet. Reopen if a game with one working link still sits not Ready for ten minutes.
Sign in to join this conversation.
No labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
cmoriarty/sports-breaker#137
No description provided.