spawn-test: Windows process-tree kill is best-effort (follow-up #9) #13
Reference in New Issue
Block a user
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Follow-up from PR #11 supervisor review (item 4).
On Windows,
proc.kill()only kills the direct child (e.g.npx), not grandchildren (node, the actual server). This is the same concern family as issue #9 (Restart Claude Desktop) — blanket process-tree termination on Windows needs careful scoping to avoid killing unrelated processes.Options to explore:
taskkill /T /F /PID <pid>for tree-kill on Windowssubprocess.CREATE_NEW_PROCESS_GROUP+os.kill(proc.pid, signal.CTRL_BREAK_EVENT)as a gentler alternativeConstraint: Cannot test locally on macOS. Any fix needs a Windows CI matrix job or manual verification note in the PR.
Cross-reference: issue #9 (Restart Claude Desktop) has the same Windows process-targeting concern.