Repository navigation
fix(http): retry Windows excluded ephemeral-port bind failures - #86
Merged
Merged
Conversation
This was referenced Oct 29, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Independent G4 reliability fix (not part of native transport PR #85)
Base: Glaze main
27b1a07b3d928111287d9280d23e00254ff3b6d5. Under PR #85 Windows CI the actual native WebView2 e2e passed all checks including 24 parallel GLZ1 invokes, but a subsequentraco glaze verifyover the explicit HTTP adapter failed because random candidate TCP port49777was unavailable (Windows WinError 10013).Root cause:
start-server-on-free-portintentionally catchesexn:fail:network?and tries a different candidate. Butstart-serverlaunches the accept loop asynchronously; whenwait-accepting!times out it incorrectly throwsexn:fail:contract?viaraise-arguments-error. That prevents the documented retry policy from running.Change: narrowly classify the failed accepting probe as
exn:fail:network(with continuation marks) after shutting down the failed listener; preserve original diagnostic text and 3-second deadline. Other API argument validation and token/cross-origin trust rules do not change.Acceptance: CI three-platform Racket matrix plus Windows agent verify step green at exact PR head, then merge. Keep this PR separate from #85 because the issue is the HTTP adapter's port allocator, not the FFI callback bridge. If this patch is rejected, the CI issue remains open rather than masking it.
No local Racket is available in this environment, so PR CI is the execution evidence. Related issue #76 and consumer PR turlamai/hackdigest#10.