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
Upgrading the dsh runtime while the profile keeps older @deepseek-ai/dsh-* packages fails startup without an actionable hint
#8751
dsh runtime: 0.1.5-rc.3 → 0.2.0-rc.2 (npm global install)
Two independent homes, each with its own web profile
Trigger: upgrading the runtime while the profile still resolves older @deepseek-ai/dsh-* packages
Symptom
After upgrading the runtime, the Web app does not come up. Two different-looking failures, same cause:
Server side — the process exits:
dsh: disabling profile plugin row "session": Plugin @deepseek-ai/dsh-session@0.1.5-rc.3 is incompatible with dsh 0.2.0-rc.2: peerDependencies {...}
... (one such line per stale row) ...
dsh: startup failed: 3 required plugins did not activate
Failed plugins (1):
typert-loader
typert-loader: @deepseek-ai/dsh-llm invocation "@deepseek-ai/dsh-llm#llm/discoverModels" parameter codec has no create() factory
Plugins waiting for services (18):
agent-loop (required) sessions
webserver (required) webStartup
connection (required) webRuntime
...
Browser side — the page shows Failed to load plugins with roughly 22 client plugins pending, all waiting on missing shortcuts / layout / uiWorkspace services.
Neither message says that the profile dependencies are stale, so it reads like a front-end bug or "the service didn't start".
Reproduction (isolated home, no user data)
export DSH_HOME=<tmp-home>
dsh plugin --profile web add @deepseek-ai/dsh-web-app@0.1.5-rc.3 # official bundle pinned to the OLD version
npm i -g @deepseek-ai/dsh@0.2.0-rc.2 # upgrade the runtime only
DSH_HOME=<tmp-home> dsh web --port <p> --no-open # -> startup failed, non-zero exit
What is NOT the cause (also verified)
A single third-party plugin with a mismatched peer range does not break anything. With only dsh-mobile-theme@0.5.0 in the profile, the runtime logs skipping profile bundle "dsh-mobile-theme" and the UI still renders normally with 0 console errors.
So the failure is specific to official @deepseek-ai/dsh-* packages that the profile resolves at older versions and that therefore shadow the runtime's newer ones.
Suggested improvements
When the profile contains @deepseek-ai/dsh-* at versions inconsistent with the running runtime, emit one aggregated message (list + fix command such as reinstalling the profile dependencies) instead of N per-row disabling ... lines.
Make the startup summary name the root cause. Right now it only reports 3 required plugins did not activate, which points at the symptom (typert-loader) rather than at the stale profile.
On the Web side, when the client plugin set no longer matches the server, show an actionable hint (e.g. "server was upgraded — reinstall the profile dependencies and reload") instead of a long pending list.
Happy to test a patch if useful; I currently run from the published npm artifact rather than a source checkout.
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.
Environment
0.1.5-rc.3→0.2.0-rc.2(npm global install)@deepseek-ai/dsh-*packagesSymptom
After upgrading the runtime, the Web app does not come up. Two different-looking failures, same cause:
Server side — the process exits:
Browser side — the page shows
Failed to load pluginswith roughly 22 client plugins pending, all waiting on missingshortcuts/layout/uiWorkspaceservices.Neither message says that the profile dependencies are stale, so it reads like a front-end bug or "the service didn't start".
Reproduction (isolated home, no user data)
What is NOT the cause (also verified)
A single third-party plugin with a mismatched peer range does not break anything. With only
dsh-mobile-theme@0.5.0in the profile, the runtime logsskipping profile bundle "dsh-mobile-theme"and the UI still renders normally with 0 console errors.So the failure is specific to official
@deepseek-ai/dsh-*packages that the profile resolves at older versions and that therefore shadow the runtime's newer ones.Suggested improvements
@deepseek-ai/dsh-*at versions inconsistent with the running runtime, emit one aggregated message (list + fix command such as reinstalling the profile dependencies) instead of N per-rowdisabling ...lines.3 required plugins did not activate, which points at the symptom (typert-loader) rather than at the stale profile.Happy to test a patch if useful; I currently run from the published npm artifact rather than a source checkout.
All reactions