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
{{ message }}
Repository navigation
[Bug] Windows: ops_bash 常驻子进程导致命令挂起,job_kill 连带终止 adb server #814
AI 提交声明:本 issue 由 AI 助手(DeepSeek Harness agent)在用户授权下代为提交。若格式或信息不规范影响处理,请多包涵;需要补充日志或最小复现时,我收到通知后会尽快提供。内容已确认不含个人信息、凭据、设备标识或本地绝对路径。
English TL;DR — On Windows, any ops_bash call that leaves a long-lived child (e.g. adb start-server) never completes and is promoted to a background job; killing that job also kills the child daemon, dropping the device connection. Separately, a corrupted private Bash runtime (Niubash ... link count mismatch) disabled all Bash calls with retry: never.
环境
dsh-ops 0.5.1(npm 包,desktop profile)
Windows,工具自带的 MSYS Bash 运行时
典型场景:用 ops_bash 连续驱动 adb(无线调试)操作安卓设备
现象
1. 留下常驻子进程的命令不会返回
ops_bash 每次是全新 shell,所以调用 adb 前需要先 adb start-server。adb server 常驻,于是调用在超时后被提升:
[still running after 120000ms; moved to background job bash-...]
Activity
fix(shells): state the process-tree reach of job kills in promoted re…
Thatgfsj commentedon Nov 20, 2026
#1033(main
c70633da,commitabb2d6f0)交付了本单最关键的可见性修复:job_kill的杀伤范围现在在模型可见处明说——src/shells/host-contract.ts:49的 promoted 渲染与docs/usage.md:279都写明它会终止整棵进程树,连同命令启动并仍挂在管道上的 daemon(adb server、dev-server watcher),处置方式是先在独立通道停掉这些 daemon,或从一开始就用run_in_background,让「是否整棵树」成为刻意决定。本单第 2 条「杀伤范围可见」即此。第 1 条要求的「执行器只等前台 shell 退出、不追踪孤儿进程」的分离语义属宿主 subprocess/jobs 层;本单报告里也写了「若属于 DSH jobs 层麻烦转给对应仓库」。dsh-ops 侧能交付的是把该边界变成可见决策的 guidance,已落地。
第 3 条另有
src/bash-runtime-failure.ts:8–25的失败分类:可恢复的 staging 失败不再被判retry: never(docs/troubleshooting.md:144)。真正 detached 的宿主机语义如需变更,请在宿主仓库另开单。fix(shells): state the process-tree reach of job kills in promoted re…