Repository navigation
Handle concurrent kv writes for token refresh - #666
Closed
cursor[bot] wants to merge 1 commit into
Closed
cursor[bot] wants to merge 1 commit into
cursor[bot] wants to merge 1 commit into
Conversation
Implement retry logic for KV writes to handle rate limiting on grant updates. Co-authored-by: jenn.muengtaweepongsa <jenn.muengtaweepongsa@sentry.io>
Contributor
Author
|
Cursor Agent can help with this pull request. Just |
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.
Add retry logic to Cloudflare KV
putoperations for OAuth grant keys to prevent 429 errors during concurrent token refreshes.Concurrent OAuth token refresh attempts can lead to multiple writes to the same Cloudflare KV grant key within a second. Cloudflare KV enforces a strict 1 write/second limit per key, causing subsequent writes to fail with a "429 Too Many Requests" error. This change introduces a retry mechanism with a linear backoff specifically for
grant:keys, allowing the second attempt to succeed after a short delay, thus serializing the writes and preventing the error.