Skip to content

fix(ci): require native boundary responses after bounded reset retries - #14

Merged
2217173240 merged 1 commit into
mainfrom
xinyu/native-smoke-boundary-retry
Oct 10, 2026
Merged

2217173240 merged 1 commit into
mainfrom
xinyu/native-smoke-boundary-retry

Conversation

@2217173240

Copy link
Copy Markdown
Owner

Main’s Windows AMD64 native check failed while reading the HTTP response to a hostile loopback POST (ConnectionResetError: WinError 10054, run 38034106161). Setup GET had passed; the log does not establish the reset’s cause.

The smoke helper now retries only connection-reset exceptions before an HTTP response, at most three attempts. Each Host/Origin case must still independently receive HTTP 403. Persistent resets, accepted requests, wrong HTTP status, and unrelated transport/protocol errors fail; response handles are closed. Production launcher behavior is unchanged.

Validation: all 10 native helper tests passed, including six new regression methods and an actual loopback server that disconnects before returning 403 for both headers; a freshly built macOS ARM64 native-channel executable passed setup, sanitized status, both boundaries, and graceful stop. Independent read-only 6.1 Sol review found no actionable issue. Existing test_native*.py CI discovery includes the regression file.

Exception handling follows the Python urllib error model: HTTPError is handled before its URLError parent; only an actual reset reason is retried. Cloud native installation checks remain required before merge.

@2217173240
2217173240 merged commit 9b531c1 into main Oct 10, 2026
16 checks passed
@2217173240
2217173240 deleted the xinyu/native-smoke-boundary-retry branch October 10, 2026 07:45
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