Checks: a followed live game whose match page lists no streams takes every check, so the next game gets none before kickoff #185

Closed
opened 2026-11-17 01:14:42 -05:00 by cmoriarty · 0 comments
Owner

What happens

On 2026-11-17 (build 9542642, checks one at a time), two followed games listed only by sportsurge were inside the lead:

  • Tahiti vs. Cook Islands (sportsurge-70206, kickoff 05:30 UTC) was checked 55 times between 05:02:58 and 06:10:38, every 71 s.
    • Every check failed the same way: "no stream found; the match page lists no streams".
    • Each check fetched the match page through the solver (SportsurgeAdapter.candidates, about 10.5 s a check), so the site was read 55 times for a page that never changed.
  • Malaysia vs. Yemen (sportsurge-70207, kickoff 06:00) entered the 30-minute lead at 05:30 and got no check until it went live.
    • At 05:40, GET /api/readiness showed waiting_first_read: 1, with Tahiti's check in flight.
    • Its first check came at 06:02:16, 31 s after the app saw it go live (06:01:45).
    • After that the two games took turns, each checked about every 141 s.

Malaysia's page listed no streams either, so nothing was lost that night. But if it had listed streams at 05:40, the game would not have been Ready at kickoff, and its background channel would not have been open.

Why

prewarm._plan_round fills a round's slots in a fixed order. Step 6 is readiness for the live games with no stream; step 8, readiness for the upcoming games inside the lead, comes after it.

With one slot, a live game with no stream is due every round, because a failed read keeps nothing. So step 8 never runs while that lasts.

Nothing passes such a game over. _check_reads skips a game whose links are all cooling, or one its list did not carry (#72). A match page that lists no streams has no links, so neither rule applies.

#115 had the same shape: a played game's standby search took every round from a live game's first check. It was fixed with a turn owed.

Done when

  • A game inside the lead that has had no first check gets one within a round or two, even while a live game keeps failing every check.
  • A match page that listed no streams is not read again every round. It waits a few minutes, or until the hub's next refresh (HUB_TTL_SECONDS), the way #72 waits for the list.
  • Tests:
    • With a live game whose page lists no streams beside an upcoming game inside the lead, the upcoming game's first check comes within two rounds.
    • The live game's checks are spaced out rather than taken every round.
## What happens On 2026-11-17 (build 9542642, checks one at a time), two followed games listed only by sportsurge were inside the lead: - **Tahiti vs. Cook Islands** (sportsurge-70206, kickoff 05:30 UTC) was checked 55 times between 05:02:58 and 06:10:38, every 71 s. - Every check failed the same way: "no stream found; the match page lists no streams". - Each check fetched the match page through the solver (`SportsurgeAdapter.candidates`, about 10.5 s a check), so the site was read 55 times for a page that never changed. - **Malaysia vs. Yemen** (sportsurge-70207, kickoff 06:00) entered the 30-minute lead at 05:30 and got no check until it went live. - At 05:40, `GET /api/readiness` showed `waiting_first_read: 1`, with Tahiti's check in flight. - Its first check came at 06:02:16, 31 s after the app saw it go live (06:01:45). - After that the two games took turns, each checked about every 141 s. Malaysia's page listed no streams either, so nothing was lost that night. But if it had listed streams at 05:40, the game would not have been Ready at kickoff, and its background channel would not have been open. ## Why `prewarm._plan_round` fills a round's slots in a fixed order. Step 6 is readiness for the live games with no stream; step 8, readiness for the upcoming games inside the lead, comes after it. With one slot, a live game with no stream is due every round, because a failed read keeps nothing. So step 8 never runs while that lasts. Nothing passes such a game over. `_check_reads` skips a game whose links are all cooling, or one its list did not carry (#72). A match page that lists no streams has no links, so neither rule applies. #115 had the same shape: a played game's standby search took every round from a live game's first check. It was fixed with a turn owed. ## Done when - A game inside the lead that has had no first check gets one within a round or two, even while a live game keeps failing every check. - A match page that listed no streams is not read again every round. It waits a few minutes, or until the hub's next refresh (`HUB_TTL_SECONDS`), the way #72 waits for the list. - Tests: - With a live game whose page lists no streams beside an upcoming game inside the lead, the upcoming game's first check comes within two rounds. - The live game's checks are spaced out rather than taken every round.
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#185
No description provided.