Repository navigation
fix(openai): protect rotated oauth credentials from enrichment timeout and race conditions - #8671
Merged
Wei-Shaw merged 1 commit intoNov 20, 2026
Conversation
Contributor
|
All contributors have signed the CLA. ✅ |
Contributor
Author
|
I have read the CLA Document and I hereby sign the CLA |
riofutab
added a commit
to riofutab/sub2api
that referenced
this pull request
Nov 13, 2026
riofutab
added a commit
to riofutab/sub2api
that referenced
this pull request
Nov 13, 2026
riofutab
added a commit
to riofutab/sub2api
that referenced
this pull request
Nov 13, 2026
- Claude 链路:令牌轮换后 401 同账号重试,per-turn beta 保留轮次输出配置,Stainless 版本头与抬升后的 UA 对齐(Wei-Shaw#8737 Wei-Shaw#8742 Wei-Shaw#8731 Wei-Shaw#8726 Wei-Shaw#8724 Wei-Shaw#8698)。 - Codex/OpenAI 链路:Desktop 独立上下文原样转发并删除 fork 的 bootstrap 扫描器,分叉会话沿用父会话缓存键,刷新后的令牌在补充信息超时时仍保存(Wei-Shaw#8680 Wei-Shaw#8664 Wei-Shaw#8671 Wei-Shaw#8735 Wei-Shaw#8682 Wei-Shaw#8703)。 - 构建:Go 升到 1.27.4 修复 GO-2026-6859(Wei-Shaw#8670);前端 Gemini 用量条刷新不再跳动(Wei-Shaw#8740)。 - fork 带的 Wei-Shaw#8034 测试改为断言轮换后的凭据被保存,并为测试桩补齐 CAS 方法。 - 后端全量 unit、golangci-lint、前端 lint/typecheck/账号组件测试通过;repository 集成测试未跑。
…t and race conditions
xuemk
force-pushed
the
fix/openai-oauth-token-rotation-persistence
branch
from
November 16, 2026 16:01
00e6d89 to
fb52c6e
Compare
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 subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Summary
This PR addresses critical edge-case failures during OpenAI OAuth token rotation where rotated credentials (access_token,
refresh_token, and expires_at) could be lost or overwritten due to downstream enrichment timeouts or concurrent settings updates.
Problem
refresh_token, subsequent account metadata enrichment (e.g. ChatGPT privacy/account checks) runs under the same attempt context. If enrichment times out or parent context cancels, the entire operation failed without saving the rotated credentials to PostgreSQL. Because OpenAI OAuth refresh tokens are single-use / rotated upon refresh, the old token is invalidated and the account becomes permanently unauthenticated (invalid_grant).
Solution
Verification