Fix concurrent token refresh race condition#190
Merged
Conversation
WebSocket起動と最初のツール呼び出しが同時にrefreshAccessToken()を 呼ぶ競合状態を修正。_refreshLockプロミスで直列化し、Workerへの リフレッシュリクエストを1回に制限。孤児refresh tokenによる セッション跨ぎの認証切れを防止。 Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
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
2 participants
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
Refs #189
WebSocket起動と最初のツール呼び出しが同時に
refreshAccessToken()を呼ぶ競合状態を修正。_refreshLockプロミスで同時リフレッシュを直列化し、Workerへのリクエストを1回に制限する。_refreshLock変数を追加し、リフレッシュ中は同じプロミスを共有finallyブロックでロックを確実に解放Test plan
~/.github-webhook-mcp/oauth-tokens.jsonの refresh_token が一貫していることを確認🤖 Generated with Claude Code