-
Notifications
You must be signed in to change notification settings - Fork 433
feat(storage): Add check for writeHandle before reansforming write_object_spec to append_object_spec #15224
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #15224 +/- ##
==========================================
- Coverage 92.94% 92.94% -0.01%
==========================================
Files 2394 2394
Lines 215552 215592 +40
==========================================
+ Hits 200345 200382 +37
- Misses 15207 15210 +3 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
b6b6ff5 to
c298039
Compare
scotthart
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Reviewable status: 0 of 5 files reviewed, all discussions resolved (waiting on @ddelgrosso1)
google/cloud/storage/internal/async/handle_redirect_error.cc line 28 at r3 (raw file):
for (auto const& rpc_status_detail : rpc_status.details()) { google::storage::v2::BidiWriteObjectRedirectedError error = google::storage::v2::BidiWriteObjectRedirectedError{};
google::storage::v2::BidiWriteObjectRedirectedError error;
Code quote:
google::storage::v2::BidiWriteObjectRedirectedError error =
google::storage::v2::BidiWriteObjectRedirectedError{};
This change will only allow transformation from write_obejct_spec to append_object_spec when error has write handle, because the failure without write handle needs write_object_spec as input for retry.
This change is