[ChuckBuilds]

Summary

Four scoreboard harness runs were fetching live from ESPN. That made them non-deterministic, and two of them rendered a blank Upcoming screen. All changes are to test fixtures only; runtime behavior is unchanged.

Baseball and football: stale schedule keys (1.51.2, 3.15.2)

#524 moved the schedule cache to f"{sport_key}_schedule_window_{lookback}_{lookahead}". These fixtures still seeded the old season keys, so every Recent and Upcoming render missed the cache and fetched the frozen window live. Those games are all final now, so Upcoming drew nothing.

Plugin	Old fixture key	New key
baseball-scoreboard	mlb_schedule_2026	mlb_schedule_window_14_7
football-scoreboard	nfl_schedule_2025	nfl_schedule_window_14_7

14_7 is the schema default (14-day lookback, 7-day lookahead), and neither harness config overrides it. The basketball equivalent landed separately in #549; merging main here cancels out the duplicate.

Lacrosse: harness no longer touches the network (1.33.2)

Each run made 112 live ESPN requests. After freeze_time ended, it also fetched next season's schedule (20270101-20270601).

• Why the refresh thread always runs. freezegun gives the real clock to calls made close to a thread's run(). The SwitchRefresh thread that display() starts therefore always sees its manager as due and calls update(). Football and baseball do the same, but their update() reads only the seeded cache and finishes inside the freeze. Lacrosse's update() went to the network:
  • other_games_min_quality defaults to "ranked", so every update() fetched the live NCAA poll. The poll is held in memory, so the fixture can't seed it. It also made which fixture games passed the filter depend on that day's poll.
  • The live manager fetched today's scoreboard on every render. With no live games it polls on its idle back-off, not on the update_intervals.live: 9999999999 the fixture relied on to stop it.
• Where 2027 came from. The last refresh thread was still waiting on the network when the freeze ended. Its next schedule read used the real date (September, so next season).
• What changed in the fixture. It now sets filtering.other_games_min_quality: "any" and test_mode: true, and drops the interval guard that did nothing. test_mode has been passed through to the managers since the fixture's old note said it wasn't.

Hockey: harness no longer touches the network (1.37.2)

Same live-manager pattern as lacrosse: 16 live scoreboard?dates= requests per run, one per render, despite update_intervals.live: 9999999999. The fixture now sets test_mode: true and drops the guard. Result: 0 requests across 3 runs, and all 16 frames pixel-identical to before. Hockey's committed goldens cover only the celebration screens, so they're unaffected.

Lacrosse (ncaa_mens_lacrosse_schedule_2026) and F1 (f1_schedule_2026) schedule keys were also checked. Their code still builds season-year keys, which match the fixtures at the frozen dates.

Verification

Ran the core harness from a fresh git archive origin/main of LEDMatrix (6cfcf2e3), on this branch after merging main. Each run was wrapped so that every requests call is logged with its thread name and then blocked.

Plugin	Before	After
baseball	3 "ESPN rejected the date range" lines; mlb_upcoming blank at 8/8 sizes (fill warning caught 5)	0 requests; 0 blank
football	2 rejected lines; nfl_upcoming blank at 8/8 sizes (fill warning caught 5)	0 requests; 0 blank
hockey	16 live scoreboard?dates= requests from the live manager	0 requests across 3 runs; frames unchanged
lacrosse	112 requests: rankings and standings from the main and SwitchRefresh threads, and today's scoreboard; then a 2027 fetch after the freeze ended	0 requests across 3 runs; all 16 frames pixel-identical to before

Blank means getbbox() is None on *_upcoming.png.

check_version_bump.py --base origin/main passes for all three plugins. update_registry.py is in sync, and the module-collision check is clean.

🤖 Generated with Claude Code

[coderabbitai]

Important

• 🔍 Trigger review

This repository does not receive automatic reviews because it has fewer than 10 stars.

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Advanced

Run ID: c5de11ad-e628-4aeb-88b8-a79de29d2cec

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

[codacy-production]

Up to standards ✅

🟢 Issues 0 issues

Results:
0 new issues

View in Codacy

_{NEW Get contextual insights on your PRs based on Codacy's metrics, along with PR and Jira context, without leaving GitHub. Enable AI reviewer
TIP This summary will be updated as you push new changes.}