Checks: a watched game's standby search starves the first check of a followed live game #115
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#115
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?
A followed live game went 18 minutes without one check, because every read went to a watched game's standby search. It was ready about a minute after a check was asked for by hand.
What happens
Seen live on 2026-11-08 (1.2.0). The owner followed the Bengals and Liverpool at 15:20Z; both games were live.
From 15:20 to 15:39 the Bengals game had no check at all. All the while, the Now table showed it as next, with an ETA of about 100 s.
Why:
prewarm.tick()fills one read slot per round (READ_CONCURRENCY, default 1). It goes in this order:The idea
Done when
now.nextnames the standby search when that is what the round takes, and a waiting game's ETA includes the reads ahead of it.Closing: merged to develop in PR #119 (merge
73f86a3), milestone 39. It deploys once nobody is watching.What changed:
Not seen live yet: a watched game's fruitless standby search giving way to a waiting game.
Deployed 2026-11-08 17:27:26Z: commit
73f86a3, container a07efdae03b6, 36.6 s down, no errors in the log. Live: the Now table's next showed Falcons vs. Bengals' check with an ETA counting down.