Bill 4fec5826bb fix: initialize dev database on API startup to prevent stale job blocking ...

- Add database initialization to API lifespan event handler
- DEV mode: Reset database on startup (unless PRESERVE_DEV_DATA=true)
- PROD mode: Ensure database schema exists
- Migrate from deprecated @app.on_event to modern lifespan context manager
- Fixes 400 error "Another simulation job is already running" on fresh container starts

This ensures the dev database is reset when the API server starts in dev mode,
preventing stale "running" or "pending" jobs from blocking new job creation.

2025-11-02 15:20:51 -05:00

..

__init__.py

feat: transform to REST API service with SQLite persistence (v0.3.0)

2025-10-31 11:47:10 -04:00

database.py

feat: add skip status tracking for job orchestration

2025-11-02 09:35:58 -05:00

date_utils.py

feat: implement date range API and on-demand downloads (WIP phase 2)

2025-10-31 16:40:50 -04:00

job_manager.py

fix: handle 'skipped' status in job_detail_status updates

2025-11-02 09:49:50 -05:00

main.py

fix: initialize dev database on API startup to prevent stale job blocking

2025-11-02 15:20:51 -05:00

model_day_executor.py

fix: correct BaseAgent initialization parameters in ModelDayExecutor

2025-11-02 09:00:09 -05:00

models.py

feat: transform to REST API service with SQLite persistence (v0.3.0)

2025-10-31 11:47:10 -04:00

price_data_manager.py

test: add comprehensive test suite for v0.3.0 on-demand price downloads

2025-10-31 17:13:03 -04:00

runtime_manager.py

feat: transform to REST API service with SQLite persistence (v0.3.0)

2025-10-31 11:47:10 -04:00

simulation_worker.py

feat: add skip status tracking for job orchestration

2025-11-02 09:35:58 -05:00