Page MenuHomePhabricator

[keyserver] Update user fetching to use new user_container column
ClosedPublic

Authored by ashoat on May 10 2024, 8:41 AM.
Tags
None
Referenced Files
F3364985: D11988.id40077.diff
Mon, Nov 25, 6:07 AM
Unknown Object (File)
Fri, Nov 22, 12:43 PM
Unknown Object (File)
Thu, Nov 21, 2:21 AM
Unknown Object (File)
Thu, Nov 21, 2:20 AM
Unknown Object (File)
Thu, Nov 7, 7:15 PM
Unknown Object (File)
Wed, Nov 6, 3:00 PM
Unknown Object (File)
Sat, Nov 2, 5:12 PM
Unknown Object (File)
Sat, Nov 2, 8:54 AM
Subscribers
None

Details

Summary

This diff updates the keyserver code for fetching a user's avatar to look at the new user_container column.

Depends on D11987

Test Plan

I tested the whole stack with the following steps:

  1. Ran the migration on a backup of my production keyserver database from September 2023. Confirm that the uploads table has the new column, that it has an index, and that it's populated for all cases where the old column matched a user. Confirm that only 32 rows were updated, which matched the number of users with avatars in a prior query
  2. Create a brand new database. Confirm that the Confirm that the uploads table has the new column, and that it has an index. Make sure DESCRIBE uploads; matches what it looked like in step 1
  3. Run the migration on my local multi-keyserver testing database. Make sure I'm still able to log in with an existing user. Confirm I can change the existing user's avatar to a photo and that there are no errors in the logs. Confirm that the avatar is still there if I log out and back in
  4. On the same database, try creating a new user with a photo avatar and confirm that it works, and that there are no errors in the logs. Confirm that the avatar is still there if I log out and back in
  5. Ran git grep container in the keyserver folder and reviewed every result to consider whether it needs to be updated

Diff Detail

Repository
rCOMM Comm
Lint
No Lint Coverage
Unit
No Test Coverage

Event Timeline

keyserver/src/fetchers/user-fetchers.js
126–131

No changes occurred here. I just wanted to make sure the columns were no more than 80 chars long

161–163

No changes occurred here. I just wanted to make sure the columns were no more than 80 chars long

This revision is now accepted and ready to land.May 13 2024, 1:44 AM