Fix: Handle gRPC precondition failures while creating object #2838
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
This change addresses an issue identified in b/378625027 where gRPC precondition failures were not being handled correctly.
Previously, error handling only checked for HTTP status codes, but gRPC uses error code 9 for precondition failures. This update adds explicit handling for gRPC error code 9 to ensure proper detection and management of precondition failures in gRPC calls.
Additionally, gRPC tests are enabled for the rename_dir_limit test package to improve test coverage .
Note: Handling of rpc codes for the different flows will be taken seperately.
Link to the issue in case of a bug fix.
NA
Testing details