v1.1.1
Patch release for #38, follow-up to 1.1.0.
Fixed
- A run that could not create its own history row (SQLite
database is lockedpast the busy timeout, a full disk) used to vanish: no row, no notification, one line in the container log, so a scheduled sync looked as if it had never fired. It is now reported on the configured notification channels as a failed run (without a run number) and the single-run lock is released as usual (#38). - The SQLite database now uses
synchronous=NORMALwith WAL, so a commit no longer fsyncs on every task-log line, and the busy timeout is 30 s instead of 5 s. A disk that stalls for a few seconds under a running backup (a VM on spinning disks, for instance) no longer turns a task-log write intodatabase is lockedand a failed run. In WAL this remains safe across an application crash; a power loss can at worst lose the last few seconds of run history, never corrupt the file (#38).
Docker
catubba/joulenap:1.1.1 (also :latest), digest sha256:c6485c912ee51341f3d8958c7cb5d06656ad0b78d5c8ce16b34ef20867947d77.
Full changelog: https://github.com/Joulenap/joulenap/blob/main/CHANGELOG.md