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)
Wed, Dec 18, 9:34 AM
Unknown Object (File)
Wed, Dec 18, 9:34 AM
Unknown Object (File)
Wed, Dec 18, 9:33 AM
Unknown Object (File)
Wed, Dec 18, 9:33 AM
Unknown Object (File)
Thu, Nov 28, 2:48 PM
Unknown Object (File)
Nov 17 2024, 11:48 PM
Unknown Object (File)
Nov 10 2024, 7:50 AM
Unknown Object (File)
Nov 10 2024, 1:07 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
No Lint Coverage
Unit
No Test Coverage