Update checker stamps update/lastCheck before the check runs — a failed/offline check suppresses retries for 24h #37
Reference in New Issue
Block a user
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Found in audit of
main@06326e5._maybe_auto_check_updates()(bcc.py~L1507) writesupdate/lastCheck = time.time()before starting the worker. If the machine is offline at launch (common: laptop wakes, app auto-starts), the failed check still counts, and no retry happens for 24 h. Repeated offline launches can starve the check indefinitely.Proposed fix: move the
setValue("update/lastCheck", …)into the completion handler, only whenrelease is not None(or at least only when the request completed). Keep the pre-check read/throttle as is.Acceptance: simulate
fetch_latest_release → Noneat startup:update/lastCheckis not advanced; a subsequent launch checks again. Successful check advances it.