[3/3] Bump grpc to 1.33.1 to fix corruption when downloading CAS blobs#13106
Closed
scele wants to merge 1 commit intobazelbuild:masterfrom
Closed
[3/3] Bump grpc to 1.33.1 to fix corruption when downloading CAS blobs#13106scele wants to merge 1 commit intobazelbuild:masterfrom
scele wants to merge 1 commit intobazelbuild:masterfrom
Conversation
Member
meteorcloudy
left a comment
There was a problem hiding this comment.
Why the jar files are appeared as moved instead of deleted then added?
Contributor
Author
I think it's a github UI glitch. Git shows that the files are changing: |
1840cfc to
33ac15d
Compare
Member
|
OK, thanks! |
Member
|
FYI @coeuvre |
Member
|
@scele Thank you for the PR series! I think this would be ready to merge, now that the other two are in. Could you please rebase this, so that we can get a clean CI run before merging it? |
Part 3: remove 1.32.x from third_party/grpc. grpc-java versions 1.27 through 1.32 had a bug where messages could arrive after the call was reported clsoed. In the case of bazel, this meant that in GrpcCacheClient, onNext could be called after onError. This leads to offset bookkeeping getting out of sync, and corrupts the CAS blob download. bazelbuild#12927
33ac15d to
77e7661
Compare
Contributor
Author
|
@meteorcloudy @philwo rebased! |
Member
|
Thanks, merging this now! |
Member
|
Thank you so much! Now merged! |
philwo
pushed a commit
that referenced
this pull request
Mar 15, 2021
Part 3: remove 1.32.x from third_party/grpc. grpc-java versions 1.27 through 1.32 had a bug where messages could arrive after the call was reported clsoed. In the case of bazel, this meant that in GrpcCacheClient, onNext could be called after onError. This leads to offset bookkeeping getting out of sync, and corrupts the CAS blob download. #12927 Closes: #13106
philwo
pushed a commit
that referenced
this pull request
Mar 15, 2021
Part 3: remove 1.32.x from third_party/grpc. grpc-java versions 1.27 through 1.32 had a bug where messages could arrive after the call was reported clsoed. In the case of bazel, this meant that in GrpcCacheClient, onNext could be called after onError. This leads to offset bookkeeping getting out of sync, and corrupts the CAS blob download. #12927 Closes: #13106
indragiek
pushed a commit
to specto-dev/bazel
that referenced
this pull request
Mar 30, 2021
Part 3: remove 1.32.x from third_party/grpc. grpc-java versions 1.27 through 1.32 had a bug where messages could arrive after the call was reported clsoed. In the case of bazel, this meant that in GrpcCacheClient, onNext could be called after onError. This leads to offset bookkeeping getting out of sync, and corrupts the CAS blob download. bazelbuild#12927 Closes: bazelbuild#13106
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Part 3: remove 1.32.x from third_party/grpc.
grpc-java versions 1.27 through 1.32 had a bug where messages could arrive
after the call was reported clsoed. In the case of bazel, this meant that
in GrpcCacheClient, onNext could be called after onError. This leads to
offset bookkeeping getting out of sync, and corrupts the CAS blob download.
#12927