A game the hub doesn't list is re-checked every minute #72

Closed
opened 2026-11-01 02:18:18 -05:00 by cmoriarty · 1 comment
Owner

What happens

On 2026-10-31, Johns Hopkins vs. Muhlenberg was checked 102 times between 17:02 and 20:09 UTC, and every check failed. From 18:32 on it was checked once a round, every 63 s or so. 92 of the checks failed with the same reason: "the site's list does not carry this game (or could not be read just now)". 88 of the 109 checks logged after the 18:18 deploy were this one game.

Why

SportsurgeAdapter.candidates raises that error before the game has a ladder. The readiness rotation (prewarm._readiness_jobs) passes over a game only when its ladder has no fresh link (ladder.has_fresh). With no ladder, there is nothing to consult, so the game is due every round.

What it costs

  • No site is bothered. The hub's list is cached (HUB_TTL_SECONDS, 5 min), so these checks don't fetch anything.
  • The history fills up. The event log keeps 2,000 events, and this one game would write about 1,400 a day. It crowds out the History section, and it swamps the Admin page's counts: 89 failed checks against 19 verified since the deploy.

The idea

A game the hub doesn't list waits for the hub's next refresh of its section before it is checked again. The answer can't change until the list does.

Default: a repeat of the same failure for the same game is logged only when its reason changes, so the history shows the first "not on the list" and then the game's next real result.

## What happens On 2026-10-31, Johns Hopkins vs. Muhlenberg was checked 102 times between 17:02 and 20:09 UTC, and every check failed. From 18:32 on it was checked once a round, every 63 s or so. 92 of the checks failed with the same reason: "the site's list does not carry this game (or could not be read just now)". 88 of the 109 checks logged after the 18:18 deploy were this one game. ## Why `SportsurgeAdapter.candidates` raises that error before the game has a ladder. The readiness rotation (`prewarm._readiness_jobs`) passes over a game only when its ladder has no fresh link (`ladder.has_fresh`). With no ladder, there is nothing to consult, so the game is due every round. ## What it costs - **No site is bothered.** The hub's list is cached (`HUB_TTL_SECONDS`, 5 min), so these checks don't fetch anything. - **The history fills up.** The event log keeps 2,000 events, and this one game would write about 1,400 a day. It crowds out the History section, and it swamps the Admin page's counts: 89 failed checks against 19 verified since the deploy. ## The idea A game the hub doesn't list waits for the hub's next refresh of its section before it is checked again. The answer can't change until the list does. **Default:** a repeat of the same failure for the same game is logged only when its reason changes, so the history shows the first "not on the list" and then the game's next real result.
Author
Owner

Deployed 2026-11-01 07:49 UTC at develop 2eb6d74 (PR #75); archived in c53ad34. A game the hub doesn't list now waits for the hub's next refresh (5 min) and is logged once; covered by test_prewarm.py. Closing; reopen if the history fills with one game again.

Deployed 2026-11-01 07:49 UTC at develop 2eb6d74 (PR #75); archived in c53ad34. A game the hub doesn't list now waits for the hub's next refresh (5 min) and is logged once; covered by `test_prewarm.py`. Closing; reopen if the history fills with one game again.
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#72
No description provided.