Retry transient Windows launcher cleanup failures - #2858
Conversation
Codex Review SummaryThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
|
Independent Terra high review: SHIP, no causal HIGH/CRITICAL blocker. Only fresh Match authorizes taskkill; persistent Unknown and PID reuse fail closed; state removal remains gated by process exit and port proof. Reviewer ran no tests. Root focused6pass and isolatedBash4pass; broad96pass/2skip/2cancelled remains documented and tracked under #2378. All five logs were copied and hash-verified into .claude/local/milestone-20260909/preserved-2561-cleanup/.tmp/issue-2561 before plain worktree removal. Source branch190251b84 is pushed. Hosted qualification and maintainer review are still required. |
The Windows launcher can retain PID state after one transient StartTime read failure or one state-file lock. Retry Unknown identity reads for up to one second, requiring a fresh Match before termination, and retry state removal only after process exit and port release are proved. Persistent uncertainty and PID reuse still fail closed.
Verification:
The probes establish both cleanup mechanisms, not which caused each historical failure. Maintainer review remains required because regression coverage touches scripts/ci. No release or repository settings change.
Refs #2561.