Problem: The awf-cli-proxy startup handshake fails on dual-stack Linux hosts where Docker resolves localhost → [::1], but the DIFC proxy binds only on IPv4 0.0.0.0:18443. With a 2-attempt fail-fast, the entire run is aborted before the agent is ever invoked.
Context: github/gh-aw#38202. Affected: PR Sous Chef, Issue Monster, Daily Code Metrics (2026-06-09 17:30–19:19 UTC). Engine-agnostic — both Copilot and Claude affected.
Root Cause: In actions/setup/sh/start_cli_proxy.sh, the readiness probe uses localhost which resolves to [::1] on dual-stack hosts. The proxy binds IPv4-only, so [::1]:18443 returns ECONNREFUSED. Fail-fast exits after only 2 retries.
Proposed Solution:
- Change the readiness probe in
start_cli_proxy.sh to use explicit 127.0.0.1 instead of localhost, or bind the proxy on :: (dual-stack) to accept both [::1] and 127.0.0.1.
- Increase retry count from 2 to ≥10 with exponential backoff to tolerate transient blips.
- Add diagnostic logging distinguishing "proxy not reachable" from "proxy not yet ready".
Generated by Firewall Issue Dispatcher · 380.5 AIC · ⊞ 27.8K · ◷
Problem: The
awf-cli-proxystartup handshake fails on dual-stack Linux hosts where Docker resolveslocalhost→[::1], but the DIFC proxy binds only on IPv40.0.0.0:18443. With a 2-attempt fail-fast, the entire run is aborted before the agent is ever invoked.Context: github/gh-aw#38202. Affected: PR Sous Chef, Issue Monster, Daily Code Metrics (2026-06-09 17:30–19:19 UTC). Engine-agnostic — both Copilot and Claude affected.
Root Cause: In
actions/setup/sh/start_cli_proxy.sh, the readiness probe useslocalhostwhich resolves to[::1]on dual-stack hosts. The proxy binds IPv4-only, so[::1]:18443returnsECONNREFUSED. Fail-fast exits after only 2 retries.Proposed Solution:
start_cli_proxy.shto use explicit127.0.0.1instead oflocalhost, or bind the proxy on::(dual-stack) to accept both[::1]and127.0.0.1.