You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
[Bug] 0.2.2-rc.5 desktop auto-update leaves official optional bundles at rc.3 — preflight disables session-query-sqlite, sessionController unavailable
#13730
Root cause chain (traced in the running host via the built-in inspector)
SessionController injects 13 services, including sessionQuery.
The profile still contains @deepseek-ai/dsh-session-query-sqlite@0.2.2-rc.3 (pulled in by dsh-experimental-session-search@0.2.2-rc.3). pluginPackages resolves the session-query-sqlite row to that profile copy, which shadows the installation's rc.5 copy.
dsh-app-boot's compatibility preflight denies the row:
disabling profile plugin row "session-query-sqlite":
Plugin @deepseek-ai/dsh-session-query-sqlite@0.2.2-rc.3 is incompatible with dsh 0.2.2-rc.5:
requirements {"@deepseek-ai/dsh-session":"0.2.2-rc.3", ...}
→ row.disabled = true for session-query-sqlite.
Nothing provides sessionQuery, so session-controller (and session-reference, ui-deliverables) stay pending. session/create and session/list both belong to sessionController, hence the new-session failure and the empty history.
This is the same failure signature as #13627 (bare-name install_bundle pulling older experimental packages). The difference here is the trigger: the desktop app's own auto-update moved the runtime to rc.5 but left the previously installed official optional bundles pinned at rc.3, without any user action in the plugin manager.
Management gaps that make this unrecoverable from the UI
pluginManager.listBundles() reports the three bundles as version: "0.2.2-rc.5", availability: "installation", installed: true — even though the profile actually resolves and runs rc.3 copies. The version drift is invisible.
"<name> is not a third-party package installed in this profile"
(bundle.official === true).
pluginManager.removeBundle(name) also refuses (not removable), so the stale copies cannot be managed away.
Result: the only supported way out is the compatibility exemption below; upgrading or reinstalling through the plugin UI is impossible.
Steps to reproduce
On 0.2.2-rc.3, install the official optional bundle @deepseek-ai/dsh-experimental-session-search (its dependency set pins dsh-session-query-sqlite@0.2.2-rc.3 into the profile).
Let the desktop app auto-update to 0.2.2-rc.5 (nightly) and restart.
Click "New session" (or switch workspaces). The error above appears and the history list is empty.
Expected behavior
The app updater should re-align profile-pinned official bundles with the new runtime, or offer a supported "repair profile" action.
An optional backend denied by the compatibility preflight should fall back to the installation-provided copy, or at least the gateway error should name the denied plugin and the compatibility reason.
listBundles() should report the version that is actually resolved, not the installation's version.
Workaround (verified across restart)
Grant the exact-version exemption the compatibility warning itself recommends, in ~/.dsh/profiles/<profile>/compatibility.json:
After a restart, sessionQuery/sessionController are active and session/list returns all 43 sessions. The exemption is exact-version, so it must be re-granted after every runtime update until the bundle versions are aligned.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Environment
0.2.2-rc.5(nightly channel), macOS arm64 (Darwin 27.2.0, Apple M4)desktop(Electron-managed)0.2.2-rc.3:@deepseek-ai/dsh-experimental-session-search@0.2.2-rc.3@deepseek-ai/dsh-experimental-terminal-bundle@0.2.2-rc.3@deepseek-ai/dsh-experimental-inspector-profile@0.2.2-rc.3Symptom
After the desktop app auto-updated from
0.2.2-rc.3to0.2.2-rc.5and restarted:新建会话失败: gateway/service-unavailable: typert gateway: session/create: active Service "sessionController" is unavailable~/.dsh/sessionsstill contains 84 files / ~63 MB.Root cause chain (traced in the running host via the built-in inspector)
SessionControllerinjects 13 services, includingsessionQuery.The profile still contains
@deepseek-ai/dsh-session-query-sqlite@0.2.2-rc.3(pulled in bydsh-experimental-session-search@0.2.2-rc.3).pluginPackagesresolves thesession-query-sqliterow to that profile copy, which shadows the installation's rc.5 copy.dsh-app-boot's compatibility preflight denies the row:→
row.disabled = trueforsession-query-sqlite.Nothing provides
sessionQuery, sosession-controller(andsession-reference,ui-deliverables) stay pending.session/createandsession/listboth belong tosessionController, hence the new-session failure and the empty history.This is the same failure signature as #13627 (bare-name
install_bundlepulling older experimental packages). The difference here is the trigger: the desktop app's own auto-update moved the runtime to rc.5 but left the previously installed official optional bundles pinned at rc.3, without any user action in the plugin manager.Management gaps that make this unrecoverable from the UI
pluginManager.listBundles()reports the three bundles asversion: "0.2.2-rc.5",availability: "installation",installed: true— even though the profile actually resolves and runs rc.3 copies. The version drift is invisible.pluginManager.updateBundle(name, "0.2.2-rc.5")refuses:(
bundle.official === true).pluginManager.removeBundle(name)also refuses (not removable), so the stale copies cannot be managed away.Result: the only supported way out is the compatibility exemption below; upgrading or reinstalling through the plugin UI is impossible.
Steps to reproduce
0.2.2-rc.3, install the official optional bundle@deepseek-ai/dsh-experimental-session-search(its dependency set pinsdsh-session-query-sqlite@0.2.2-rc.3into the profile).0.2.2-rc.5(nightly) and restart.Expected behavior
listBundles()should report the version that is actually resolved, not the installation's version.Workaround (verified across restart)
Grant the exact-version exemption the compatibility warning itself recommends, in
~/.dsh/profiles/<profile>/compatibility.json:{ "@deepseek-ai/dsh-session-query-sqlite@0.2.2-rc.3": ["0.2.2-rc.5"] }After a restart,
sessionQuery/sessionControllerare active andsession/listreturns all 43 sessions. The exemption is exact-version, so it must be re-granted after every runtime update until the bundle versions are aligned.Related discussions
@deepseek-ai/dsh-*packages (same preflight mechanism, CLI path)TL;DR (中文)
0.2.2-rc.5 桌面端自动更新后,profile 里官方可选 bundle 仍钉在 rc.3,兼容性预检把
session-query-sqlite行禁用,sessionQuery缺失导致SessionController不激活,新建会话与历史列表全部失效(数据未丢失)。listBundles谎报 rc.5,updateBundle拒绝 official bundle,UI 无法自助修复。临时方案是compatibility.json精确版本豁免。All reactions