-
Notifications
You must be signed in to change notification settings - Fork 432
feat(storage): Add full object checksum validation at finalization for json path #15815
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
base: main
Are you sure you want to change the base?
Conversation
Summary of ChangesHello @v-pratap, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed! This pull request enhances the Google Cloud Storage client library by implementing full object checksum validation for resumable uploads. It introduces mechanisms to calculate and transmit Highlights
Using Gemini Code AssistThe full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips. Invoking Gemini You can request assistance from Gemini at any point by creating a comment using either
Customization To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a Limitations & Feedback Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here. You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension. Footnotes
|
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.
Code Review
This pull request adds support for sending object checksums (CRC32C and MD5) in the final chunk of a resumable upload for the JSON/REST transport. The changes look good and are well-tested. I've found a couple of minor issues related to leftover debugging code that should be addressed before merging.
Codecov Report❌ Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## main #15815 +/- ##
==========================================
+ Coverage 92.94% 92.95% +0.01%
==========================================
Files 2458 2458
Lines 227585 227725 +140
==========================================
+ Hits 211531 211685 +154
+ Misses 16054 16040 -14 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
This PR modifies the client library to send the x-goog-hash header, containing crc32c= and/or md5= values, if available, when sending the final chunk of a resumable upload.
Implementation Details
The core of the change involves coordinating hash calculation between the ObjectWriteStreambuf and the RestStub. The hash_function within ObjectWriteStreambuf maintains the running checksum state for the entire upload.
RestStub::UploadChunk:
For intermediate chunks (when last_chunk() is false), UploadChunk receives a valid hash_function_ptr from ObjectWriteStreambuf. It calls hash_function->Update() to incorporate the chunk's payload into the running checksum.
For the final chunk (when last_chunk() is true), UploadChunk receives a nullptr for hash_function_ptr but receives the final, computed object hashes via request.known_object_hashes(). It then adds the x-goog-hash header(s) to the HTTP request using these final hashes.
ObjectWriteStreambuf::FlushFinal:
This method is called when Close() is invoked on the stream.
It first calls hash_function->Update() with any data still pending in its internal buffer.