Replies: 1 comment
|
Added a plugin-boot runbook for this failure: distinguish direct settings entries from include-chain entries, stop systemd Restart=on-failure loops, then remove one authoritative declaration in a copied profile and verify unique loader IDs. The guide treats the uncaught error as a recoverable configuration boundary, not a browser cache issue. https://github.com/sandbaseai/deepseek-harness-handbook/releases/tag/v0.5.398 |
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.
环境
cd5ef81481(release/dsh-0.1.2-alpha.1)node --import tsx/esm apps/cli/src/bin.ts web --no-open现象
运行过程中插件树加载失败,进程以未捕获异常退出。systemd 服务配置了
Restart=on-failure+RestartSec=5,于是每 5 秒反复重启,日志里连续出现 10+ 次完全相同的报错,服务表现为"异常"状态。journal 关键日志:
相关配置
~/.dsh/settings.yaml中有:profile
web(~/.dsh/profiles/web)同时引用/安装了@deepseek-ai/dsh-agent-presets。定位
vendor/loader/src/config/group.ts:64EntryGroup.update()在 applyinclude(cordis:include)时,同一 EntryGroup 的 config 数组里出现了两个id: agent-presets的条目(一个来自 settings.yaml 直接配置,一个来自 include 链合并),loader 直接抛TypeError,随后被当作 uncaughtException 导致进程退出。建议
All reactions