-
Notifications
You must be signed in to change notification settings - Fork 938
fix(codex): harden native main refresh publication #3000
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Draft
MarcTCruz
wants to merge
8
commits into
lidge-jun:dev
Choose a base branch
from
MarcTCruz:fix/native-main-refresh-v3
base: dev
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
+1,416
−64
Draft
Changes from all commits
Commits
Show all changes
8 commits
Select commit
Hold shift + click to select a range
ce87094
fix(codex): harden native main token refresh
MarcTCruz 128a7ed
fix(codex): validate native refresh recovery journals
codex acf6b60
fix(codex): harden native main refresh recovery
MarcTCruz 88bdf21
fix(codex): preserve symlinked native auth targets
MarcTCruz a007832
fix(codex): preserve displaced auth writers
MarcTCruz 58b6c7b
fix(codex): guard refresh recovery exchange races
MarcTCruz c3570d4
fix(codex): retain concurrent recovery writers
MarcTCruz 1582dec
fix(codex): revalidate recovery symlink target
MarcTCruz File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
Oops, something went wrong.
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🗄️ Data Integrity & Integration | 🟠 Major | ⚡ Quick win
Do not discard rotated credentials after a successful token exchange.
At line 267 the upstream refresh already succeeded and
refreshedholds a rotated refresh token. Line 274 then throws and discards it whenever the signal is aborted, so the new grant is never written toauth.json.The abort is easy to trigger. Line 241 aborts the shared controller as soon as the last waiter leaves
waitForNativeMainRefresh, which happens when the only waiting client disconnects. Line 208 also aborts afterNATIVE_MAIN_REFRESH_WAIT_MS, and the response can arrive just after that timer fires.Failure mode: OAuth refresh grants rotate. After the server issues the new refresh token, the presented token can be invalid. The stored
auth.jsonthen holds a dead grant, every later refresh fails, and the account needs interactive reauthentication. A single client disconnect at the wrong moment is enough.Persist the refreshed credentials first, then report the cancellation. The write remains safe because it still runs under the exclusive claim and
publishNativeMainRefreshverifies the expected content before replacing the file.🐛 Proposed fix
📝 Committable suggestion
🤖 Prompt for AI Agents