Page MenuHomePhabricator

[identity] Send RETRY for transaction conflicts
ClosedPublic

Authored by bartek on Oct 2 2024, 1:07 AM.
Tags
None
Referenced Files
Unknown Object (File)
Sun, Nov 10, 7:50 AM
Unknown Object (File)
Sun, Nov 10, 1:07 AM
Unknown Object (File)
Fri, Nov 8, 10:38 PM
Unknown Object (File)
Fri, Nov 8, 1:48 PM
Unknown Object (File)
Oct 16 2024, 7:20 PM
Unknown Object (File)
Oct 13 2024, 5:35 PM
Unknown Object (File)
Oct 13 2024, 9:31 AM
Unknown Object (File)
Oct 13 2024, 6:33 AM
Subscribers

Details

Summary

Part of ENG-9427.

  • Added a function that checks if DDB error is transaction conflict (we already have one but this one is more opinionated)
  • Added a case to handle_db_error to send retry tonic message instead of unexpected error

Depends on D13567

Test Plan

Simulated TransactionConflictException DDB error and checked gRPC status code in a UI client

Diff Detail

Repository
rCOMM Comm
Lint
Lint Not Applicable
Unit
Tests Not Applicable