Repository navigation
test(g01): distinguish broker header capture boundaries - #168
Merged
jjangg96 merged 2 commits intoNov 13, 2026
Merged
Conversation
Codex Review Summary: ✅ CompletedThis 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. |
Contributor
Author
|
@codex review |
|
Codex Review: Didn't find any major issues. Hooray! Reviewed commit: ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
If Codex has suggestions, it will comment; otherwise it will react with 👍. Codex can also answer questions or update the PR. Try commenting "@codex address that feedback". |
jjangg96
deleted the
codex/issue-1-public-ci-header-boundary-fix-2026-11-13
branch
November 13, 2026 10:08
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.
Follow-up for #1, addressing the G01 core failure in post-merge Public CI run 43403108575 on
227d6f5.The G02 client leaves
Accept-Encodingunset. A direct synthetic RoundTripper observes an empty value; the actual child command crosses Go'snet/httptransport, so its HTTPS test server observes the transport-addedgzipvalue. The shared fixture assertion now receives the expected value for each capture boundary.Verification
group-policysubcase.TestExperimentalActualCommandBrokerReceiverwith race detection and current-source helpers.TestControllerProcessHandoffV3ActualBrokerChildwith race detection.go vet -p=1 -tags=g01_pair_fixture ./livecanary.git diff --check.Test/evidence-only change; no production behavior or live canary operation. Issue #1 remains open pending the existing live acceptance gates.