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)
Tue, Feb 18, 1:14 AM
Unknown Object (File)
Tue, Feb 18, 1:13 AM
Unknown Object (File)
Tue, Feb 18, 1:13 AM
Unknown Object (File)
Tue, Feb 18, 1:13 AM
Unknown Object (File)
Jan 15 2025, 7:12 AM
Unknown Object (File)
Dec 30 2024, 9:31 PM
Unknown Object (File)
Dec 30 2024, 4:25 PM
Unknown Object (File)
Dec 25 2024, 4:42 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