-
Notifications
You must be signed in to change notification settings - Fork 12.7k
retry rate-limited write requests #28867
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
Open
notcodesid
wants to merge
1
commit into
calcom:main
Choose a base branch
from
notcodesid:fix/google-calendar-rate-limit-retry
base: main
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.
+188
−25
Open
Changes from all commits
Commits
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.
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.
Uh oh!
There was an error while loading. Please reload this page.
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.
🧩 Analysis chain
🏁 Script executed:
Repository: calcom/cal.com
Length of output: 3988
Add retryConfig to the Calendar client instantiation in callback.ts.
The gap is real. While
CalendarAuth.ts:355correctly passesretryConfig: GOOGLE_CALENDAR_RETRY_CONFIG, the constructor atcallback.ts:89instantiatesnew calendar_v3.Calendar({ auth: oAuth2Client })without it. This inconsistency leaves the callback path unprotected if it later performs write operations or is extended to do so.Apply the same
retryConfig: GOOGLE_CALENDAR_RETRY_CONFIGto the callback.ts constructor for consistency and resilience.🤖 Prompt for AI Agents
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.
yo thanks for this. i checked the callback path, but it is only used during OAuth setup to read the primary calendar via
getPrimaryCalendar(), not for the event write calls involved in #28834.im keeping this PR scoped to the Google Calendar event write path retry behavior (
insert/patch/update) and not expanding it to unrelated client construction paths.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.
@notcodesid, that's a fair scoping decision — sincecallback.tsonly callsgetPrimaryCalendar()during OAuth setup (a read), the retry config for write operations isn't applicable there. Thanks for the clarification!✏️ Learnings added
🧠 Learnings used