MUL-5155: KAP-1051: diagnose Codex thread/start timeouts fail-closed (#5759)

* fix(agent/codex): diagnose thread start timeouts (KAP-1051)

Co-authored-by: multica-agent <github@multica.ai>

* fix(agent/codex): validate thread ID before success lifecycle

Co-authored-by: multica-agent <github@multica.ai>

* fix(agent/codex): confirm process tree cleanup

Co-authored-by: multica-agent <github@multica.ai>

* fix(agent/codex): bound Windows pipe cleanup

Co-authored-by: multica-agent <github@multica.ai>

* ci: run bounded Codex cleanup test on Windows

Co-authored-by: multica-agent <github@multica.ai>

* fix(agent): reap initialize timeout process groups

* fix(agent): redact initialize timeout stderr

* fix(agent): redact initialize context failures

---------

Co-authored-by: multica-agent <github@multica.ai>
This commit is contained in:
milymarkovic
2026-07-23 10:09:50 +03:00
committed by GitHub
parent 7d6a1dfab1
commit 09dce598df
7 changed files with 793 additions and 23 deletions

View File

@@ -212,6 +212,13 @@ jobs:
# that stops matching) is visible in the log instead of passing as "ok".
run: go test ./pkg/agent -v -run '^(TestCursorExecutePromptSurvivesPowerShellShim|TestPlatformCursorInvocation|TestPlatformCopilotInvocation|TestPlatformPiInvocation)' -count=1 -timeout=5m
- name: Test bounded Codex cleanup with inherited stdout descendant
working-directory: server
# Windows cannot prove whole-tree termination without a Job Object,
# but a descendant holding inherited stdout must never keep Result
# blocked forever. -v makes RUN/PASS evidence explicit in CI logs.
run: go test ./pkg/agent -v -run '^TestCodexWindowsInheritedStdoutDescendantCleanupIsBounded$' -count=1 -timeout=5m
- name: Build Windows CLI helper entrypoint
working-directory: server
run: go build ./cmd/multica