Skip to content

fix(gateway): make passive connection failures diagnosable - #157

Merged
Pigbibi merged 1 commit into
mainfrom
codex/gateway-passive-failure-diagnostics-20261001
Oct 1, 2026
Merged

Pigbibi merged 1 commit into
mainfrom
codex/gateway-passive-failure-diagnostics-20261001

Conversation

@Pigbibi

@Pigbibi Pigbibi commented Oct 1, 2026

Copy link
Copy Markdown
Collaborator

Change

  • Normalize CRLF and silently precheck the existing temporary SSH key before any connection attempt.
  • Classify captured SSH/IAP errors into fixed categories; ambiguous messages remain unknown.
  • Validate the six allowed passive response fields and the closed set of helper blocking reasons.
  • Keep blocking responses as failures even when the SSH process exits successfully.
  • Preserve protected target matching, the default-off switch, one 75-second attempt and cleanup.

Validation

  • Six new diagnostic regressions, five metadata cases and the existing shell/Node checks passed.
  • actionlint, Python/shell syntax, Ruff and diff checks passed.
  • Independent material review passed after correcting blocked-response exit status.

No real SSH retry, broker request, VM metadata write, permission change or runtime deployment was performed. The prior connection failure remains unresolved.

@Pigbibi
Pigbibi merged commit 71c28a1 into main Oct 1, 2026
2 checks passed
@Pigbibi
Pigbibi deleted the codex/gateway-passive-failure-diagnostics-20261001 branch October 1, 2026 03:25
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant