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
At upstream commit 76fda729799fe9b3848dbe2c211d4b231032b81e (0.1.2-rc.1), the single-exe runtime manifest does not provide @deepseek-ai/dsh-session-title-llm, although the shipped base composition reaches @deepseek-ai/dsh-session-title-first-prompt-llm, which requires it as a non-optional workspace peer.
verify-runtime-closure still reports a closed graph because loadWorkspacePackages() scans packages/*/*/package.json and vendor/*/package.json, but not apps/*/package.json. The direct runtime dependency @deepseek-ai/dsh is owned by apps/cli, so traversal stops before reaching @deepseek-ai/dsh-base and its title provider.
The packaged Web profile consequently fails when that shared title-policy package is absent:
Cannot find package '@deepseek-ai/dsh-session-title-llm' imported from
.../@deepseek-ai/dsh-session-title-first-prompt-llm/lib/index.js
Expected behavior
The runtime closure gate should traverse every workspace package reachable from the deploy root, including application packages, and fail before packaging whenever a required workspace peer is not supplied.
Tested workaround
Add this direct runtime dependency and update the lockfile:
After a frozen reinstall and complete rebuild, the title-policy import succeeds. The resulting executable proceeds to Web initialization, where the separate SEA client-module issue described in the next report becomes visible.
Suggested upstream direction
Add apps/*/package.json to loadWorkspacePackages() in scripts/verify-runtime-closure.ts.
Add @deepseek-ai/dsh-session-title-llm to python/sdk-runtime/package.json and update pnpm-lock.yaml.
Add a regression proving that the unmodified runtime manifest fails if this peer is removed and that the diagnostic includes the complete runtime -> dsh -> base -> provider -> peer chain.
No credentials or live API request are required to reproduce this packaging failure.
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.
Summary
At upstream commit
76fda729799fe9b3848dbe2c211d4b231032b81e(0.1.2-rc.1), the single-exe runtime manifest does not provide@deepseek-ai/dsh-session-title-llm, although the shipped base composition reaches@deepseek-ai/dsh-session-title-first-prompt-llm, which requires it as a non-optional workspace peer.verify-runtime-closurestill reports a closed graph becauseloadWorkspacePackages()scanspackages/*/*/package.jsonandvendor/*/package.json, but notapps/*/package.json. The direct runtime dependency@deepseek-ai/dshis owned byapps/cli, so traversal stops before reaching@deepseek-ai/dsh-baseand its title provider.中文摘要:当前单文件运行时遗漏了
dsh-session-title-llm。现有闭包检查没有扫描apps/*,因此错误地报告依赖图 closed。Environment
76fda729799fe9b3848dbe2c211d4b231032b81e0.1.2-rc.1v24.19.011.7.0node24-linux-x64Reproduction
From a clean checkout, the authoritative runtime manifest contains
@deepseek-ai/dshbut not@deepseek-ai/dsh-session-title-llm:Observed closure output with the clean manifest:
The dependency chain omitted from that traversal is:
The packaged Web profile consequently fails when that shared title-policy package is absent:
Expected behavior
The runtime closure gate should traverse every workspace package reachable from the deploy root, including application packages, and fail before packaging whenever a required workspace peer is not supplied.
Tested workaround
Add this direct runtime dependency and update the lockfile:
After a frozen reinstall and complete rebuild, the title-policy import succeeds. The resulting executable proceeds to Web initialization, where the separate SEA client-module issue described in the next report becomes visible.
Suggested upstream direction
apps/*/package.jsontoloadWorkspacePackages()inscripts/verify-runtime-closure.ts.@deepseek-ai/dsh-session-title-llmtopython/sdk-runtime/package.jsonand updatepnpm-lock.yaml.runtime -> dsh -> base -> provider -> peerchain.No credentials or live API request are required to reproduce this packaging failure.
All reactions