Admin: the Sites section lists every site with its last 24 hours and why one is held back #109

Closed
opened 2026-11-07 23:48:58 -05:00 by cmoriarty · 2 comments
Owner

Part of #103. On the mockup canvas, Picked column: Sites · 3B.

What happens

The owner's questions about the section today:

  • The count: "Sites" shows a number of sites used this hour, which reads as arbitrary.
  • The colours: do the yellow and red bars mean something is broken?
  • No way to learn more about a site that looks broken.
  • The table: is it every site the app supports, the ones in use now, or the failing ones? And why are they all red?

They were red because the app's own browser is challenged before the solver hands off, which looks like a ban (#98).

The idea

  1. Every site the app reads, in two groups: Game lists, and Player pages.
  2. Filter tabs with counts: All, Game lists, Player pages, Held back.
  3. One row per site:
    • the host;
    • 48 half-hour cells over the last 24 hours: worked (green), played from (blue), held back or Cloudflare (amber), refused (red), idle (grey);
    • a Now column: a ✓ for working, ▶ for playing now, or for a held-back site a clock with the time until its next try and a Try now button (POST /api/sources/{host}/clear, which exists).
  4. Hovering a cell or a stretch gives its time range and, as chips, the cause (Cloudflare, refused with its status), how many tries, whether it cleared by itself, and how many new games were found meanwhile.
  5. The list shows 14 sites and a "19 more" button for the rest.

Data it needs

New: per-host half-hour buckets for 24 hours.

  • Counts per bucket: reads, verified, played from, challenged, held back, refused (403/429/503).
  • Where it is kept: on disk under DATA_DIR, so a restart doesn't wipe the day.
  • courtesy.snapshot() keeps only last-hour counts today.

Also new: each site's group (game list or player page) and the deadline of its next try, as an epoch.

Done when

  • In the unit lane:
    • buckets roll over every half hour;
    • 24 hours are kept and read back after a restart;
    • a held-back host reports its next-try deadline.
  • In the frontend tests:
    • the rows render in their two groups;
    • the filter counts match the fixture;
    • a held-back row shows its countdown and Try now.
Part of #103. On the [mockup canvas](https://claude.ai/artifact/81TFkGA3agPRSmkL38L4yJ), Picked column: **Sites · 3B**. ## What happens The owner's questions about the section today: - **The count:** "Sites" shows a number of sites used this hour, which reads as arbitrary. - **The colours:** do the yellow and red bars mean something is broken? - **No way to learn more** about a site that looks broken. - **The table:** is it every site the app supports, the ones in use now, or the failing ones? And why are they all red? They were red because the app's own browser is challenged before the solver hands off, which looks like a ban (#98). ## The idea 1. **Every site the app reads,** in two groups: Game lists, and Player pages. 2. **Filter tabs with counts:** All, Game lists, Player pages, Held back. 3. **One row per site:** - the host; - 48 half-hour cells over the last 24 hours: worked (green), played from (blue), held back or Cloudflare (amber), refused (red), idle (grey); - a Now column: a ✓ for working, ▶ for playing now, or for a held-back site a clock with the time until its next try and a **Try now** button (`POST /api/sources/{host}/clear`, which exists). 4. **Hovering a cell or a stretch** gives its time range and, as chips, the cause (Cloudflare, refused with its status), how many tries, whether it cleared by itself, and how many new games were found meanwhile. 5. **The list shows 14 sites** and a "19 more" button for the rest. ## Data it needs New: per-host half-hour buckets for 24 hours. - **Counts per bucket:** reads, verified, played from, challenged, held back, refused (403/429/503). - **Where it is kept:** on disk under DATA_DIR, so a restart doesn't wipe the day. - `courtesy.snapshot()` keeps only last-hour counts today. Also new: each site's group (game list or player page) and the deadline of its next try, as an epoch. ## Done when - **In the unit lane:** - buckets roll over every half hour; - 24 hours are kept and read back after a restart; - a held-back host reports its next-try deadline. - **In the frontend tests:** - the rows render in their two groups; - the filter counts match the fixture; - a held-back row shows its countdown and Try now.
Author
Owner

Deployed 2026-11-08 06:11Z in PR #111 (merge a133e29, container 71367c5163eb); OpenSpec change archived in b4d5b94. Live now: every site the app reads, grouped into game lists and player pages, each with 48 half-hour cells over 24 h (kept in sites.json across restarts) and a countdown with Try now when held back. The strips start empty at this deploy and fill as sites are read. Left open until a day of strips has been seen.

Deployed 2026-11-08 06:11Z in PR #111 (merge a133e29, container 71367c5163eb); OpenSpec change archived in b4d5b94. Live now: every site the app reads, grouped into game lists and player pages, each with 48 half-hour cells over 24 h (kept in sites.json across restarts) and a countdown with Try now when held back. The strips start empty at this deploy and fill as sites are read. Left open until a day of strips has been seen.
Author
Owner

Closed at the owner's word (2026-11-08): the fix is merged to develop in PR #111 (merge a133e29) and deployed. A new issue will be opened if a problem shows up.

Closed at the owner's word (2026-11-08): the fix is merged to develop in PR #111 (merge a133e29) and deployed. A new issue will be opened if a problem shows up.
Sign in to join this conversation.
No labels
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#109
No description provided.