Repository navigation
[Bug] Desktop update fails: "Host did not complete graceful task teardown (graceful deadline exceeded)" — 0.2.1-rc.2 → 0.2.1-rc.3, win32 x64 #11274
PetrichorIRIS
started this conversation in
General
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Summary
Desktop auto-update from 0.2.1-rc.2 → 0.2.1-rc.3 fails every time with:
The installer downloads and verifies correctly; the failure is entirely in the graceful shutdown step before install.
Environment
@deepseek-ai/dsh-desktop0.2.1-rc.2nightlyhttps://download.deepseek.com/dsh-desk/feeds/win-x64/D:\DeepSeek Harness\What was ruled out
The downloaded artifact is fine — the update package is not the problem:
Also ruled out: disk space (66 GB free), file permissions, network reachability (feed + binary both download fine).
Timeline (2026-10-28)
The verified installer is still sitting in
pending\afterwards, confirming download succeeded and only teardown failed.Likely cause: a plugin/task blocks teardown past the deadline
This profile has 18 third-party bundles / 245 plugin rows. Several of them own background lifecycles that plausibly outlive a short grace window:
dsh-mnemon(+17 sub-packages) — memory system withidleReviewMs: 30000timer@nanmicoder/dsh-agent-teams— multi-agent team, may hold active tasksdsh-better-sidebar— file watchers / sidebar services@yuxianglin/dsh-bridge-browser— websocket carrier daemondsh-free-search/dsh-find-plugin— in-flight network fetchesdshmarket— market connectionIf graceful shutdown waits on host tasks without a hard cancel for extension-owned tasks, a deadline miss is inevitable.
Suggested fixes
SIGKILLthe whole child process tree instead of failing the update.Workaround (works today)
Run the already-downloaded, signature-verified installer manually while the app is closed:
or download directly:
This bypasses the teardown step and installs successfully.
Note
No
crash-*.logwas produced for this event — the log directory's newest entry is still 2026-10-24. A graceful-shutdown timeout is silent, which makes it hard to diagnose from the user side.All reactions