Page MenuHomePhabricator

[keyserver] Create a blob while adding / editing an invite link
ClosedPublic

Authored by tomek on Dec 1 2023, 6:55 AM.
Tags
None
Referenced Files
Unknown Object (File)
Wed, May 1, 7:47 AM
Unknown Object (File)
Sat, Apr 27, 3:18 AM
Unknown Object (File)
Mar 6 2024, 9:13 AM
Unknown Object (File)
Mar 6 2024, 9:13 AM
Unknown Object (File)
Mar 6 2024, 9:13 AM
Unknown Object (File)
Mar 6 2024, 9:13 AM
Unknown Object (File)
Mar 6 2024, 9:13 AM
Unknown Object (File)
Mar 6 2024, 9:12 AM
Subscribers

Details

Summary

Every time we're creating / updating a link, we need to make sure that the blob is created.
We start with blob creation because it is a shared place between keyservers and links should be globally unique - a keyserver should first check if a blob can be created which means that other keyservers haven't used that link.

Depends on D10131

Test Plan

Create a link and check if a correct blob is created.
Update a link and check if a blob is created and an old blob holder is deleted.

Diff Detail

Repository
rCOMM Comm
Lint
Lint Not Applicable
Unit
Tests Not Applicable

Event Timeline

Delete unnecessary export

tomek requested review of this revision.Dec 1 2023, 7:22 AM

Looks good to me, but it would be nice if someone with more context on this could take a look as well

This revision is now accepted and ready to land.Dec 5 2023, 8:29 AM
tomek planned changes to this revision.Dec 6 2023, 1:44 AM

I'm going to check the option of using MariaDB transactions to minimize the number of possible race conditions

This revision is now accepted and ready to land.Feb 1 2024, 6:47 AM

I'm going to check the option of using MariaDB transactions to minimize the number of possible race conditions

Not sure which idea I was investigating, but I remember concluding that introducing transactions would cause even more issues.