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
唯一的痕迹是启动时 stdout 里的一行 dsh: warning: 1 entry did not activate
也就是说:一条脏记录 → 整块定时任务功能消失,而且是静默的。
Reproduction
在 $DSH_HOME/storages/schedule.json 中给任意一条任务的 prompt 末尾加一个 \n(或经由任何不做 trim 的写入路径落下这样一条记录)
重启 dsh
观察启动日志与定时任务行为
本次实际数据(脱敏):
"prompt": "执行每日远程日志分析日报任务……需要关注项条数。\n"
Current behavior
启动日志:
dsh: warning: 1 entry did not activate
schedule (@deepseek-ai/dsh-schedule): DomainError: domain 'schedule':
stored record 'schedule-43a1d7b4-…' in table 'tasks' does not match its schema
ZodError: [ { "code": "custom",
"message": "ScheduleLogError: schedule prompt must be non-empty and already trimmed",
"path": [ "record" ] } ]
英文摘要:A single stored task record whose prompt ends with a newline makes the whole schedule domain fail to activate at startup, so every scheduled task silently stops — in our case for 48.5 hours, while the process, ports and UI all looked healthy. The only trace was one dsh: warning: 1 entry did not activate line on stdout. A malformed record should be skipped (or auto-trimmed) with a visible warning, instead of taking down all scheduling.
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
自托管的 dsh(
--profile web)上配置了 4 条每日定时任务。其中一条任务记录的prompt末尾多了一个换行符(这条数据来自 UI 之外的写入路径),服务启动时整个 schedule 域加载失败,调度器没有激活,4 条任务全部停止投递。实际影响:静默停摆 48.5 小时(2026-11-13 16:48 → 2026-11-15 17:17)。期间:
active、Web 界面正常、端口正常dsh: warning: 1 entry did not activate也就是说:一条脏记录 → 整块定时任务功能消失,而且是静默的。
Reproduction
$DSH_HOME/storages/schedule.json中给任意一条任务的prompt末尾加一个\n(或经由任何不做 trim 的写入路径落下这样一条记录)本次实际数据(脱敏):
Current behavior
启动日志:
行为:
补充:存储层的写入路径本身是 trim 的(
dsh-schedule/lib/index.js里 create/update 都有const normalizedPrompt = prompt.trim()),所以这条记录来自带外写入。但下面「Expected behavior」的容错仍然值得做——带外写入之外,旧版本数据、手工恢复备份、外部工具同步都可能产生不合规记录,代价却是整域瘫痪。Expected behavior
建议按优先级:
期望的最低标准:一条坏记录只影响它自己,不影响其余任务;坏了要能看见。
Environment
dsh web --profile web$DSH_HOME/storages/schedule.json英文摘要:A single stored task record whose
promptends with a newline makes the wholescheduledomain fail to activate at startup, so every scheduled task silently stops — in our case for 48.5 hours, while the process, ports and UI all looked healthy. The only trace was onedsh: warning: 1 entry did not activateline on stdout. A malformed record should be skipped (or auto-trimmed) with a visible warning, instead of taking down all scheduling.All reactions