fix(system-update): apply saved updaterIntervalSeconds on daemon connect - #3093
Merged
bbedward merged 1 commit intoAug 18, 2026
Merged
Conversation
The dms daemon always initializes IntervalSeconds to its 30-minute default and has no persistence of its own; the saved SettingsData value was only ever pushed on manual interaction with the Settings UI dropdown. Result: every daemon (re)start silently reverts to checking every 30 minutes regardless of the user's configured interval.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Fixes #3092.
The daemon has no persistence and always starts at the 30min default; the saved interval was only ever pushed on manual Settings-UI interaction. Now it's re-applied on every fresh daemon connection.