Skip to content

fix(gui): keep checking for updates while the window stays open#89

Merged
ErikChevalier merged 1 commit into
mainfrom
fix/updater-while-open
Jun 11, 2026
Merged

fix(gui): keep checking for updates while the window stays open#89
ErikChevalier merged 1 commit into
mainfrom
fix/updater-while-open

Conversation

@ErikChevalier

Copy link
Copy Markdown
Contributor

Problem

The desktop update check fired only on the first window show (showEvent), once per process, plus a ~daily throttle. A user who left the app open when a release published was never notified (this is how v26.06.05 was missed). The version-code comparison itself was correct.

Fix

On first show, in addition to the launch check, start a recurring QTimer that re-runs the throttled check_if_due while the window stays open. The ~daily throttle means almost every tick is a no-op (no network); it just bounds the notification lag instead of leaving it at "never".

Verification

  • New GUI test asserts showing the window starts a recurring (non-single-shot) timer at the expected interval, throttled so it touches no network. Full suite green (ruff + mypy + 703 tests).

🤖 Generated with Claude Code

The update check ran only on the first window show, so a release published
after launch was never surfaced to a user who left the app open (no relaunch,
no notification). It now also starts a recurring timer on first show that
re-runs the throttled check while the window stays open. check_if_due keeps
the ~daily throttle, so almost every tick does no network at all; this only
bounds how long after a release the banner can lag, instead of never.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
@ErikChevalier ErikChevalier merged commit 35ea98a into main Jun 11, 2026
1 check passed
@ErikChevalier ErikChevalier deleted the fix/updater-while-open branch June 11, 2026 01:08
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant