No description
0f336b3d0c
All checks were successful
Deploy / deploy (push) Successful in 22s
The America/Phoenix TZ fix earlier only passed timezone= to BackgroundScheduler's constructor. That wasn't enough: APScheduler's CronTrigger independently calls tzlocal's get_localzone() in its own __init__ when not given an explicit timezone, regardless of what the scheduler itself is configured with. This never surfaced in testing because schedules.json was always empty — the rebuild_jobs() loop that constructs CronTrigger never executed. It crashed for real once a real schedule existed (confirmed live: the already-configured "Pokemon Singles >10" 4x/day schedule crash-looped the container on every boot). Fixed by passing the same resolved timezone to every CronTrigger call. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01H6TgffxTvYhqxykAbVQg2v |
||
|---|---|---|
| .claude/skills/deploy-massprice | ||
| .forgejo/workflows | ||
| static | ||
| templates | ||
| .env.example | ||
| .gitignore | ||
| app.py | ||
| automation.py | ||
| CLAUDE.md | ||
| docker-compose.yml | ||
| Dockerfile | ||
| gunicorn.conf.py | ||
| notify.py | ||
| requirements.txt | ||
| scheduler.py | ||
| storage.py | ||