fix(#516): review round 7 - re-arm queues behind a running slot, hashes only while the option is on, one series in memory at a time

This commit is contained in:
makiolaj committed 2026-11-14 12:19:24 +01:00
1 parent fb178a779e
commit 09c20ee90f
4 files changed
+61 -49

No files matched your search

+4 -2
View File
@@ -491,7 +491,8 @@ provider's root URI (the provider notifies every change there, whoever made it:
this app, a sync adapter or another app), a 2-minute settle delay capped at 15
minutes, and battery-not-low. A trigger fires once and observes only while its
job waits, so there are two slots: a change run arms the other one as it starts
(catching changes made during the run) and again as it ends. Runs share the
(catching changes made during the run) and again as it ends, queued behind
that slot's run if it is still running. Runs share the
scheduled backup's lock. A change run only rewrites the stable copies and never
retries: the dated files and their retention stay on the interval, so a day of
edits can't rotate the history out. Every run that writes something is recorded
@@ -499,7 +500,8 @@ on the status line; the failure notification comes once per failure streak, as
it reaches the threshold, and the next success of any run clears it. Since the
trigger fires for any provider change (reminders, other calendars, sync
bookkeeping), each series' file (events in a fixed order) is hashed without its
`DTSTAMP`s (`auto_backup_fingerprints`, reset with the folder) and a change run
`DTSTAMP`s (`auto_backup_fingerprints`, reset with the folder and kept only
while the option is on) and a change run
skips the series whose hash (bound to the copy's name) and stable copy are
unchanged, without even listing the folder when no hash moved; the hash is
dropped before a copy is rewritten. A copy that went missing is restored by the