Settings say "Sparat." while a change is still waiting to be saved #294

Closed
opened 2026-10-22 14:46:30 +00:00 by littlefox · 1 comment
Owner

Found when release PR #281's CI failed (run #472) in notifications.spec.ts: a notification was shown during quiet hours.

Cause: settings are saved a second after the last change (settings_view.rs, changed), but the label keeps the previous state meanwhile. So "Sparat." from an earlier save stays up while newer changes haven't been written. The test waited for "Sparat.", went back, and the message arrived before the quiet hours were saved. A person who sees "Sparat." and closes the app straight away is told the same thing.

Fix: "Sparar…" from the first change on, and "Sparat." only when the newest change has been written.

Found when release PR #281's CI failed (run #472) in notifications.spec.ts: a notification was shown during quiet hours. Cause: settings are saved a second after the last change (`settings_view.rs`, `changed`), but the label keeps the previous state meanwhile. So "Sparat." from an earlier save stays up while newer changes haven't been written. The test waited for "Sparat.", went back, and the message arrived before the quiet hours were saved. A person who sees "Sparat." and closes the app straight away is told the same thing. Fix: "Sparar…" from the first change on, and "Sparat." only when the newest change has been written.
Author
Owner

Fixed in #295: "Sparar…" shows from the first change, and "Sparat." only once the newest change is written. Verified: settings.spec.ts now changes a setting after "Sparat." and expects "Sparar…" within 0.5 s, then "Sparat.". settings and notifications specs passed locally on desktop, Android and iPhone; PR CI and main #476 green.

Fixed in #295: "Sparar…" shows from the first change, and "Sparat." only once the newest change is written. Verified: settings.spec.ts now changes a setting after "Sparat." and expects "Sparar…" within 0.5 s, then "Sparat.". settings and notifications specs passed locally on desktop, Android and iPhone; PR CI and main #476 green.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
littlefox/neokom#294
No description provided.