Skip to content

Conversation

@lingcoder
Copy link

…sensitivity issues #2264

What kind of change does this PR introduce?

Bug fix, feature, docs update, ...

What is the current behavior?

Please link any relevant issues here.

What is the new behavior?

Feel free to include screenshots if it includes visual changes.

Additional context

Add any other context or screenshots.

@lingcoder lingcoder requested a review from a team as a code owner November 21, 2025 07:58
@cemalkilic
Copy link
Contributor

Thanks for spotting the issue & contributing the fix @lingcoder !

Can you please also update the test?

require.Equal(t, "0x196a28d05bA75C8dC35B0F6e71DD622D1aC82b7E", parsed.Address)

@cemalkilic
Copy link
Contributor

Hello! I reviewed this PR again and a quick note on the migration.

auth.identities can be massive on some projects, and the backfill UPDATE worries me (long run time, locks). We do have an index from UNIQUE (provider_id, provider), but since provider isn’t indexed on its own, WHERE provider = 'web3' can still end up doing a big scan.

What about skipping the bulk backfill and whoever needs backfilling can run manual queries?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants