prisma-risk / tsoracle / 28899439000

95%

push

github

fix(server): make the lease-commit epoch guard atomic with the table mutation (#664)

The guard read the allocator epoch, released that lock, and only then took the lease-table lock — a step-down interleaving between the two applies the mutation to the just-cleared follower table, leaving a phantom in-memory record under a stale epoch. Checking the epoch while holding the table lock closes the window: step_down clears the allocator before it takes the table lock, so a raced commit is either refused or wiped by the subsequent table clear. The nested lock order introduced here (table, then allocator) is unique to lease_commit; every other path takes the two locks sequentially.

Signed-off-by: Sebastian Thiebaud <sebastian@prismarisk.com>

45 of 46 new or added lines in 1 file covered. (97.83%)

18383 of 19325 relevant lines covered (95.13%)

310935.98 hits per line