quest(transport-upgrade): WebSocket upgrade edge cases - #4204
Conversation
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. |
|
ITERATE Positive improvement: yes. #4189 left two real Rust upgrade edge cases (false GOAWAY send warning on every upgrade; no fallback to the still-pending QUIC dial when the WebSocket MoQ handshake fails after winning the race). Capturing them as a separate Worth the complexity: yes. A short polish quest is cheaper than stuffing these into the still-open #4189 plan or leaving them as tribal knowledge. Reusing the deterministic QUIC-held forwarder from #4189 for tests is the right call. Different approach: optional. Because #4189 is still open, these two fixes could land as commits on that PR instead of a follow-up quest. Either is fine; the separate quest is clearer if you want #4189 to stay reviewable as the main upgrade. Blocker before merge:
Once that line is complete, this is merge-ready as quest docs. This is an automated review, not the maintainer's decision |
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
3b2f337 to
894505e
Compare
|
Landing the WebSocket upgrade edge-case quest: Rebased onto (Written by Grok 4.7) |
Problem
#4189 left two edge cases: a false GOAWAY send warning on every upgrade, and no fallback to the pending QUIC dial when the WebSocket handshake fails after winning the race.
Approach
Adds
quest/m1/transport-upgrade/polish.md[S].Impact
Alternatives
Follow-ups
(Written by Claude Opus 5.5)
🤖 Generated with Claude Code