You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Updates in each machine's own hours, only when quiet; show machines that are behind #886
What: live updates the owner controls. Each machine updates only inside its update hours and only when it is quiet; the owner can see which machines are behind and tick which ones to update.
Why the owner wants it: updates must never stop running agents by surprise, but the fork should still follow upstream nightly (decided). Owner questions #147-#150 and #41 answered.
Already built: default pin and "never update unasked" #171, Fork settings rows for automatic updates #544, quiet check / busy probe #547, the go-live kit.
Left (checklist):
2 Hours window, server side: setting, pure module, tests (wrap at midnight, bad value, clock change)
3 Settings rows for the hours window
4-6 When upstream's own updater lands: check it does not lose or double-start held work, then use upstream's scheduler and settings row and delete ours (keep the fork's add-on only if the check finds a gap)
7 Client setting "leave machines with running threads unticked" (after upstream's update-dialog checkboxes land, or carry them around 11-29)
Done when: every machine updates by itself inside its hours when idle, shows "behind" otherwise, and no running agent is stopped by an update the owner did not choose.
Activity