Repository navigation
macOS: workspace create fails after app update - cua-bundle pin stays on old version, hoisted @deepseek-ai/* shadows host singleton #13490
Replies: 1 comment
|
The pin is exact, and nothing rewrites it on app update. Confirmed from source: registry installs use Your hoisting explanation also matches the documented resolution contract: bundle names prefer the installation, everything else resolves profile-first ( Your workaround is the right one; one addition — besides You can hand this to an AI to adapt it to your machine; if it resolves the issue, marking it as the answer helps the next reader. |
Uh oh!
There was an error while loading. Please reload this page.
Summary
On macOS, after the desktop app auto-updates to a new release, creating a workspace fails permanently until a manual dependency fix is applied:
The trigger is the optional Computer Use bundle (
@deepseek-ai/dsh-cua-bundle), which is pinned with an exact version in the profile'spackage.json. The pin does not follow the host app version, and because the profile installs withnodeLinker: hoisted, the bundle's transitive@deepseek-ai/*packages (e.g.dsh-storage-domain,dsh-typert-protocol,dsh-cua,dsh-experimental-cua-macos) are flattened into the profile's top-levelnode_modules, where they shadow the copies shipped with the host. The host'sworkspaceControllerservice then never activates.Environment
0.2.2-rc.2 -> 0.2.2-rc.3(also happened on0.2.2-rc.1 -> 0.2.2-rc.2)desktop;pnpm-workspace.yamlin the profile containsnodeLinker: hoistedandautoInstallPeers: falseReproduction
X, enable Computer Use. The profilepackage.jsongains"@deepseek-ai/dsh-cua-bundle": "X"(exact version, no range).Y(in-app update).package.jsonstill contains"@deepseek-ai/dsh-cua-bundle": "X"— it is not rewritten by the update/plugin-manager path.Observed package state in the broken case (profile
node_modules/@deepseek-ai/):Verified workaround
dependencies["@deepseek-ai/dsh-cua-bundle"]in~/.dsh/profiles/desktop/package.jsonto the host versionY.pnpm-lock.yamland the wholenode_modulesdirectory (an in-place install can leave orphan copies such as_c711_suffixed dirs pinned to the old version).DeepSeek Harness.app/Contents/Resources/runtime/primary-runtime/dependencies/.After the fix, all
dsh-*packages in the profile equalYand no old copies remain.Suggested fixes (any one would remove the footgun)
dependencyis an@deepseek-ai/*package, rewrite its pin to the host version when they differ (the same class of check that adsh-check-style diagnostic performs).@deepseek-ai/*from hoisting (e.g.publicHoistPattern/isolated linker), or resolve host@deepseek-ai/*packages with priority over profilenode_modules.workspaceControllercannot activate, surface which package/version caused it instead of a genericgateway/service-unavailable.Happy to provide logs or test a fix on macOS — this reproduces deterministically on every app update while Computer Use is enabled.
All reactions