ShivamandDavid Reiss ed6e7cba69 changed proto for idempotency checks (#6833) ...

## What changed?
<!-- Describe what has changed in this PR -->
- changed proto for quicker idempotency checks 
- added idempotency checks in the update handler

## Why?
<!-- Tell your future self why have you made these changes -->
- The updateHandler can receive multiple duplicate requests which might
mean we update the local state multiple times. We want a guard against
that.

## How did you test it?
<!-- How have you verified this change? Tested locally? Added a unit
test? Checked in staging env? -->
- None right now.

## Potential risks
<!-- Assuming the worst case, what can be broken when deploying this
change to production? -->
- None, going into a feature.

## Documentation
<!-- Have you made sure this change doesn't falsify anything currently
stated in `docs/`? If significant
new behavior is added, have you described that in `docs/`? -->

## Is hotfix candidate?
<!-- Is this PR a hotfix candidate or does it require a notification to
be sent to the broader community? (Yes/No) -->
- NA

2024-11-26 15:20:46 -08:00

..

v1

tdbg: --force-unload-tq-partition (#6523)

2024-10-04 11:20:24 -04:00