fix(gitlab): use default expires_in for older GitLab versions#4387
Open
tfnick wants to merge 1 commit into
Open
fix(gitlab): use default expires_in for older GitLab versions#4387tfnick wants to merge 1 commit into
tfnick wants to merge 1 commit into
Conversation
Some older GitLab versions return empty expires_in parameter during OAuth callback, causing database update errors. Now defaults to 7200 seconds (2 hours) when expires_in is not provided. Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
dosubot
Bot
added
size:XS
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
1 participant
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.
Some older GitLab versions return empty expires_in parameter during OAuth callback, causing database update errors. Now defaults to 7200 seconds (2 hours) when expires_in is not provided.
What is this PR about?
Please describe in a short paragraph what this PR is about.
Checklist
Before submitting this PR, please make sure that:
canarybranch.Issues related (if applicable)
closes #123
Screenshots (if applicable)