Replies: 1 comment 1 reply
-
|
I fixed it in two parts. First, I made the backend run a CCTV ingest immediately on startup instead of waiting for the first scheduler tick. Second, I changed the CCTV ingestors so they open and close their SQLite connection each time they run, which is much safer for background jobs and avoids connection issues over time. After that, the backend started filling cctv.db right away, /api/live-data/fast began returning real CCTV entries immediately, and the CCTV mesh on the frontend started showing feeds properly. In backend/services/data_fetcher.py, I changed startup behavior so CCTV ingestion runs immediately when the backend boots. Before, CCTV only populated on the scheduled refresh, which meant the frontend would often load first and get an empty cctv array. In backend/services/cctv_pipeline.py, I changed the CCTV ingestors so they no longer keep one long-lived SQLite connection open. Each ingest run now opens its own connection, writes the data, and closes it cleanly. That makes the scheduled/background ingest much more reliable. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
CCTV Mesh stopped displaying at v0.9.5

Had been working up to this release.
(Many thanks for this otherwise!)
Beta Was this translation helpful? Give feedback.
All reactions