agessaman dc4b7ac8fc fix: close the scheduled-message update check/write race ...

PUT verified original_schedule outside the lock, so a concurrent delete
between the check and the write resurrected the entry as a new one, and
two concurrent renames of the same original left both results present.
The existence check now runs inside _save_scheduled_message_locked
against the same snapshot the duplicate check uses, so create, update and
delete are each a single critical section.

Added a concurrency test: two simultaneous creates of one schedule now
produce exactly one 200 and one 409 with a single entry on disk.

2026-08-22 01:11:42 -07:00

..

static

fix(neighbors): update zero-hop neighbor discovery and data handling

2026-08-12 18:01:28 -07:00

templates

fix: address Codex review of tonight's work

2026-08-22 00:16:03 -07:00

__init__.py

feat: web viewer — auth, contact management, live streaming, config, maintenance, and backup

2026-03-17 18:07:18 -07:00

app.py

fix: close the scheduled-message update check/write race

2026-08-22 01:11:42 -07:00

config_panels.py

feat(core, scheduler): implement timeout handling for advert sending

2026-04-16 19:29:28 -07:00

dashboard_stats.py

fix(dashboard): narrow snr directly so mypy accepts float(snr)

2026-08-21 20:38:48 -07:00

integration.py

feat(retention): enhance data retention and resource limits for Raspberry Pi

2026-07-30 08:06:21 -07:00