-
Notifications
You must be signed in to change notification settings - Fork 0
fix(auth): serialize token refresh and make config/session writes atomic #230
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
Merged
Merged
Changes from all commits
Commits
Show all changes
3 commits
Select commit
Hold shift + click to select a range
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
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.
nit: any non-2xx here is classified as
Rejected, which makesensure_access_tokencallclear_session()and fall through to re-mint. That's correct for400 invalid_grant(the session really is dead), but it also fires for transient server failures —429 Too Many Requests,500,502/503. Under the exact 128-way burst this PR targets, an overloaded token endpoint returning 503/429 is plausible, and none of those consume/rotate the refresh token — the session is still good. Since refresh is now serialized undersession.lock, clearing on a transient 5xx/429 needlessly kills the session for the whole burst (forced re-login for interactive sessions with noapi_keyfallback), which partly undercuts the goal here.Worth treating 5xx/429 like the
Transportcase (keep the session, surface the error) and only clearing on a genuine4xx invalid_grant. Note this is still strictly better than the pre-PRErr(_) => clear_session(), so not blocking. (not blocking)