"latest" integer in AppState isn’t persistent between runs #16

Closed

opened 2026-02-21 19:57:34 +01:00 by marfavi · 2 comments

marfavi commented

2026-02-21 19:57:34 +01:00

Owner

The simulator API keeps a latest integer in AppState (an AtomicI64) which is updated from the latest query‑parameter on each request and returned by GET /latest.

Currently that value is only stored in memory and initialised to -1 when the server starts:

let app_state = Arc::new(AppState {
    …,
    latest: AtomicI64::new(-1),
});

No code ever writes it to the database or disk, so when you stop/restart the container the value is reset. This makes it impossible for the server to remember its last‑seen value across deployments.

Suggested fix: Persist the value somewhere (such as a new row in SQLite or a small file in the mounted volume) and load/update it through the existing service layer, so container rebuilds and restarts don’t lose it.

The simulator API keeps a latest integer in AppState (an AtomicI64) which is updated from the latest query‑parameter on each request and returned by GET /latest. Currently that value is only stored in memory and initialised to -1 when the server starts: ```rust let app_state = Arc::new(AppState { …, latest: AtomicI64::new(-1), }); ``` No code ever writes it to the database or disk, so when you stop/restart the container the value is reset. This makes it impossible for the server to remember its last‑seen value across deployments. Suggested fix: Persist the value somewhere (such as a new row in SQLite or a small file in the mounted volume) and load/update it through the existing service layer, so container rebuilds and restarts don’t lose it.