Use dbNoCache for OAuth identity lookups to avoid Hyperdrive cache staleness#15
Merged
Merged
Conversation
…aleness After linking an account, the cached DB client could serve stale results on the next OAuth login attempt, making it appear the link wasn't saved. Co-Authored-By: Claude Sonnet 4.6 <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
WHERE oauth_provider = ? AND oauth_sub = ?) were using the cached Hyperdrive clientoauth_subwasn't saved — causing the username prompt to appear againdbNoCachefor all four OAuth identity lookups (Google web callback, Google GET callback, Apple native, Google native)🤖 Generated with Claude Code