Skip to content
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

Verify gRPC cache downloads after flushing the output. #16072

Closed
wants to merge 1 commit into from

Conversation

benjaminp
Copy link
Collaborator

Make sure any internal buffers (especially compression) are flushed before attempting verify the digest of the downloaded file.

Make sure any internal buffers (especially compression) are flushed before attempting verify the digest of the downloaded file.
@benjaminp benjaminp requested a review from a team as a code owner August 9, 2022 18:20
@sgowroji sgowroji added team-Remote-Exec Issues and PRs for the Execution (Remote) team awaiting-review PR is awaiting review from an assigned reviewer labels Aug 10, 2022
@brentleyjones
Copy link
Contributor

Does this fix any known bug? Is it worth cherry-picking into 5.3?

@coeuvre
Copy link
Member

coeuvre commented Aug 18, 2022

I am not aware of any bugs this fixes. but should be easy to cherry-pick into 5.3 if time allows.

@brentleyjones
Copy link
Contributor

@bazel-io flag

@bazel-io bazel-io added the potential release blocker Flagged by community members using "@bazel-io flag". Should be added to a release blocker milestone label Aug 18, 2022
@benjaminp benjaminp deleted the flush-then-verify branch August 18, 2022 14:28
@ShreeM01 ShreeM01 removed the awaiting-review PR is awaiting review from an assigned reviewer label Sep 15, 2022
aiuto pushed a commit to aiuto/bazel that referenced this pull request Oct 12, 2022
Make sure any internal buffers (especially compression) are flushed before attempting verify the digest of the downloaded file.

Closes bazelbuild#16072.

PiperOrigin-RevId: 468432319
Change-Id: I9d991d563c232113fe29921580f4964c603faf58
@meteorcloudy
Copy link
Member

This should be in 6.0, removing the "potential release blocker" label.

@meteorcloudy meteorcloudy removed the potential release blocker Flagged by community members using "@bazel-io flag". Should be added to a release blocker milestone label Dec 1, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
team-Remote-Exec Issues and PRs for the Execution (Remote) team
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

7 participants