Show live Windows update progress and recover stalled downloads #35
Labels
No labels
status:done
status:in-progress
status:ready
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
rexlManu/garmith-app#35
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
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?
Settings > About stays on Downloading after its first update check. Show live progress, ready and error state there, including while a session hides the global banner. Inspect the v0.1.0 to v0.1.1 Windows updater path and add a bounded recovery if downloads stall. Verify with focused updater/UI tests; keep native Windows install validation open in #19.
Pushed
6d2d7ee. About now reads live updater state, so it shows percentage, ready and errors rather than a frozen result. Windows skips the missing old-blockmap lookup and cancels/retries after three minutes without progress. The screenshot alone does not prove that the v0.1.0 download stalled. Full typecheck/tests, release tests, built updater UI check, parity and isolated Windows x64 package checks passed locally. Main CI is pending; native Windows update validation remains in #19.Main package CI passed for
6d2d7ee. Tagged the same commit v0.1.2; tag workflow run 3285 is building and publishing. Local Windows x64 unpacked package contains builder-util-runtime, electron-updater and the Windows Koffi binary. The public release and manifests will be checked after publication.Published v0.1.2 from
6d2d7ee. Main CI run 39 and tag CI run 40 passed. All six public files returned anonymous HTTP 200. The Windows and Linux update manifests name 0.1.2 and the matching artifacts with SHA-512; the public latest-release API also returns v0.1.2. WORKFLOW.md records the checks inc9a62aa. A real Windows update remains open in #19; the original screenshot alone did not establish a network stall.