Repository navigation
test(relay): reserve the unavailable auth endpoint - #5768
Conversation
Co-Authored-By: GPT-6 <noreply@openai.com>
Co-Authored-By: GPT-6 <noreply@openai.com>
|
Warning Review limit reachedYou've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository. Next included review available in 16 minutes. View limit details
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
Codex Review SummaryThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
Co-Authored-By: GPT-6 <noreply@openai.com>
…ture Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
|
Merge summary:
Enabling auto-merge pinned to (Written by Claude Opus 5.5) |
Problem
The unavailable-auth fixture dropped its TCP listener before dialing the relay, leaving the auth port available to concurrent tests. If another listener took that port, the fixture could stall or receive an unrelated response. A workspace run hit the session-close assertion's ten-second deadline.
Approach
Retain a listening TCP endpoint for the test and close each accepted connection before answering HTTP. A scoped JoinSet owns the accept task and releases it on teardown. Assert that another listener cannot acquire the address and that an HTTP request fails, then retain the relay refusal-counter checks. Listening avoids the earlier bound-but-not-listening fixture's assumption about the operating system's TCP refusal behavior.
Impact
Validation
6b67a8194, the listening/closing fixture passes in 0.261s during the scoped suite. The focused run also passes.MOQ_STRICT=1 just checkpasses: 507 scoped relay/CLI tests and 200 CLI playback tests, plus formatting, rustdoc, dependency hygiene, drill sensitivity, flake, and repository checks. No macOS or Windows execution is claimed for this revision.Alternatives
A scripted HTTP error response would test HTTP status handling. Closing the connection instead keeps this a transport failure while reserving the port, without retries, sleeps, or a longer timeout.
Follow-ups
This remains separate from S3 coverage #5760 and admission deadline changes #5765. The earlier S3 head plus fixture revision
a88391d53passed a full Linux workspace check; #5760 records those exact inputs. Refresh S3 and its checks after this prerequisite lands. No merge is requested by this update.(written by GPT-6)