Desktop updater stale-lock and retry fixes
Cluster 85894 · apps/desktop. Data as of
Nothing open on GitHub. Fix merged in #90937. Check it covers your case.
The short answer
- Known?
- Yes. 5 related items grouped here, 1 issue already closed.
- Fix event
- A fix was merged to main in PR #90937. Check it covers your case. No release data is tracked.
- Tracker
- The maintainers' tracker marks this
resolved, deciding PR #90994. That is separate from the fix event. - Still open
- Nothing open on GitHub.
These items address a deadlock and blocking condition in the Desktop updater where stale update state prevents retries from succeeding. Two fixes target preserving holder age across handoffs and clearing stale updates after retries.
Open issues0
Open PRs0
Fixes on record
-
#90937 fix(update): Windows Desktop updates finish instead of parking on "Updating Hermes"
files:
scripts/desktop-update/windows.ps1,tests/test_desktop_update_windows_pipe_drain.py,tests/test_desktop_update_windows_python_handoff.py -
#90941 fix(installer): the bootstrap installer stops waiting on pipe EOF
files:
.github/actions/detect-changes/action.yml,.github/workflows/ci.yaml,.github/workflows/rust-tests.yml,apps/bootstrap-installer/src-tauri/src/powershell.rs,apps/bootstrap-installer/src-tauri/src/update.rs,scripts/ci/classify_changes.py,tests/ci/test_classify_changes.py -
#90994 fix(updater): preserve the holder's age across update-marker handoffs
files:
apps/bootstrap-installer/src-tauri/src/update.rs,apps/desktop/electron/main.ts,apps/desktop/electron/update-handoff-marker.test.ts,apps/desktop/electron/update-marker.test.ts,apps/desktop/electron/update-marker.ts,scripts/desktop-update/posix.sh,scripts/desktop-update/windows.ps1
1 PR closed without merging
From the close comments: merged via another change 1
-
#85964 fix(updater): let stale Desktop updates clear after retries · merged via another change →
#90994,#90937,#90941
Closed issues · 1
- Closed#85894Desktop updater deadlocks against launchd gateways, then the stale updater blocks every retry
How this cluster was grouped
-
Link evidence (
structural links throughout): every member is connected by structural evidence: shared changed files, or a closing/superseded reference. -
Pairwise link density
0.40: the share of item pairs that carry a link, counting a structural link in full and a relevance-only link at 0.36.1.00means every pair is linked.
Pick up a Lab task
Check whether a fix covers the open issues here, with your own agent. Bring back evidence for maintainers.
Open the Lab