[Bug] Tool call fails with "prepare" undefined on fresh install #7223
JasonChen-Uki
started this conversation in
General
Replies: 2 comments 1 reply
|
me too |
0 replies
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.
Environment:
Reproduction:
Expected: The Bash tool executes and returns the file list.
Actual: The turn fails immediately with:
本轮运行失败 Cannot read properties of undefined (reading 'prepare')
Additional context:
node_modules/@deepseek-ai/dsh-toolswas missing afterpnpm install. I manually created the symlink (ln -s ../../packages/core/tools node_modules/@deepseek-ai/dsh-tools) and confirmedpackages/core/tools/lib/index.jsexists. The error persists.pnpm why @deepseek-ai/dsh-toolsreturns no output, meaning no installed package depends ondsh-tools. Manually symlinking it intonode_modules/@deepseek-ai/dsh-toolsdoes not fix the error — the scheduler still fails at runtime.~/.dsh/profiles/web/cordis.ymlis an empty array[]. The profile is composed entirely from bundles listed in~/.dsh/profiles/web/package.json:["@deepseek-ai/dsh-base", "@deepseek-ai/dsh-web-app"].packages/bundle/base/package.jsoncorrectly declares@deepseek-ai/dsh-toolsand all@deepseek-ai/dsh-tool-*packages in itsdependencies. However,~/.dsh/profiles/web/node_modules/@deepseek-ai/only contains a subset that exactly mirrors the root project'sdevDependencies(dsh-agent, dsh-browser-use, dsh-computer-use, dsh-experimental-*, dsh-llm-replay, dsh-skill-office, dsh-tool-session-query, dsh-web-fetch-http).dsh-toolsand the tool packages are missing.~/.dsh/profiles/web/pnpm-workspace.yamlcontains onlypackages: - .andnodeLinker: hoisted. The profile's owndependenciesfield is empty{}. This suggests the profile dependency resolution is not followingdsh-base's transitive dependencies, but instead only mirrors the root project'sdevDependencies— which happens to not includedsh-tools.~/.dsh/logs/does not exist after a fresh run, so no DSH logs are available. The only log files in the environment are from npm and ubuntu-pro. This suggests DSH may be failing before its logging subsystem initializes.Attachments: No DSH logs are available (see item 9). A screenshot of the Web UI error is attached.

All reactions