fix(storage): Fix Resume() to use append_object_spec instead of write_object_spec for resumed appendable uploads #15558
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.
This PR corrects the logic in AsyncWriterConnectionResumedState::Resume() where it incorrectly assumed initial_request_ would always contain an write_object_spec. This assumption fails when resuming an upload that was initiated with ResumeAppendableObjectUpload, which uses append_object_spec, which leads to passing the bucket and object names empty.
The fix introduces a check to determine whether initial_request_ contains a write_object_spec or an append_object_spec, and then correctly extracts the bucket and object names from the available spec. This approach aligns with the pattern already used in WriteResultFactory for handling these two types of specifications.
This change is