Container view — Architecture
architecture-overview · hero
Per-game timeout handled as no-data miss
handle-per-game-timeout
BatchRequest → void
void → httpx.ReadTimeout
void → BatchResult
LedgerRow → void
.github/workflows/historical-refresh.yml
scripts/backfill_refresh.py
src/pipelines/sources/stats.py
src/pipelines/utils/api_client.py src/pipelines/utils/rate_limiter.py
src/schemas/003_stats.sql
scripts/backfill_refresh.py
src/pipelines/sources/stats.py
src/pipelines/utils/api_client.py src/pipelines/utils/rate_limiter.py
src/schemas/003_stats.sql
✦
✦
✦
✦
✦
✦
✦
✦
✦
✦
✦
✦
✦
✦
✦
/
What could this change break?
What should I review most carefully?
Drag to select a region · Space to pan · Drop a screenshot
↵
fix(backfill): treat a per-game advanced-box timeout like a persistent 5xx
rstover-fo/cfb-database #158
· 2 diagrams
Start the walkthrough
W
Fit the whole strip
1
Copy share link
Switch to light
Loading comments
Loading screenshots
How to move around
Ask about this canvas
/
Star
100%
Container view — Architecture
Architecture
Per-game timeout handled as no-data miss
Data flow
Resume walkthrough
↵
This diagram has a walkthrough
scroll to move through it
swipe to move through it