Set the digest_function field as part of all relevant gRPC requests#17772
Closed
EdSchouten wants to merge 1 commit intobazelbuild:masterfrom
Closed
Set the digest_function field as part of all relevant gRPC requests#17772EdSchouten wants to merge 1 commit intobazelbuild:masterfrom
EdSchouten wants to merge 1 commit intobazelbuild:masterfrom
Conversation
EdSchouten
force-pushed
the
eschouten/20230314-set-digest-function
branch
4 times, most recently
from
e693925 to
1a5e926
Compare
Contributor
Author
ShreeM01
added
team-Remote-Exec
Member
|
Please wait until #16791 is merged and rebase. Thanks! |
In the following PR we extended most of the REv2 *Request messages to take an explicit digest function: bazelbuild/remote-apis#235 This eliminates the ambiguity between digest functions that have the same hash length (e.g., MD5 and MURMUR3, SHA256 and SHA256TREE). This change extends the REv2 client in Bazel to set the digest_function field explicitly, so that the server does not need to use any heuristics to pick a digest function when processing requests. As we are now going to call DigestUtil.getDigestFunction() far more frequently, alter DigestUtil to precompute the value upon construction.
EdSchouten
force-pushed
the
eschouten/20230314-set-digest-function
branch
from
1a5e926 to
96e6596
Compare
Contributor
Author
|
Done! |
coeuvre
approved these changes
Mar 16, 2023
Member
|
Hi @coeuvre, Since I can see that this PR has been approved, please let me know whether I should proceed with importing it.Thanks! |
Contributor
Author
Contributor
|
I had a look and it SGTM. Let's import it. |
tjgq
added
awaiting-PR-merge
ShreeM01
removed
the
awaiting-PR-merge
Contributor
|
Can/should this be cherry-picked into 6.2? |
Contributor
Author
|
If it is cherry-picked into 6.2, maybe #16791 should be as well? |
fweikert
pushed a commit
to fweikert/bazel
that referenced
this pull request
May 25, 2023
In the following PR we extended most of the REv2 *Request messages to take an explicit digest function: bazelbuild/remote-apis#235 This eliminates the ambiguity between digest functions that have the same hash length (e.g., MD5 and MURMUR3, SHA256 and SHA256TREE). This change extends the REv2 client in Bazel to set the digest_function field explicitly, so that the server does not need to use any heuristics to pick a digest function when processing requests. As we are now going to call DigestUtil.getDigestFunction() far more frequently, alter DigestUtil to precompute the value upon construction. This change was tested by letting Bazel forward all traffic through an instance of bb_clientd that was patched up to require the use of `digest_function`. Closes bazelbuild#17772. PiperOrigin-RevId: 520074622 Change-Id: Ie92dc368c502b9bc3fddef56a5eb0a238760f673
brentleyjones
pushed a commit
to brentleyjones/bazel
that referenced
this pull request
Jul 25, 2023
In the following PR we extended most of the REv2 *Request messages to take an explicit digest function: bazelbuild/remote-apis#235 This eliminates the ambiguity between digest functions that have the same hash length (e.g., MD5 and MURMUR3, SHA256 and SHA256TREE). This change extends the REv2 client in Bazel to set the digest_function field explicitly, so that the server does not need to use any heuristics to pick a digest function when processing requests. As we are now going to call DigestUtil.getDigestFunction() far more frequently, alter DigestUtil to precompute the value upon construction. This change was tested by letting Bazel forward all traffic through an instance of bb_clientd that was patched up to require the use of `digest_function`. Closes bazelbuild#17772. PiperOrigin-RevId: 520074622 Change-Id: Ie92dc368c502b9bc3fddef56a5eb0a238760f673 (cherry picked from commit 0a8380b)
brentleyjones
pushed a commit
that referenced
this pull request
Jul 25, 2023
In the following PR we extended most of the REv2 *Request messages to take an explicit digest function: bazelbuild/remote-apis#235 This eliminates the ambiguity between digest functions that have the same hash length (e.g., MD5 and MURMUR3, SHA256 and SHA256TREE). This change extends the REv2 client in Bazel to set the digest_function field explicitly, so that the server does not need to use any heuristics to pick a digest function when processing requests. As we are now going to call DigestUtil.getDigestFunction() far more frequently, alter DigestUtil to precompute the value upon construction. This change was tested by letting Bazel forward all traffic through an instance of bb_clientd that was patched up to require the use of `digest_function`. Closes #17772. PiperOrigin-RevId: 520074622 Change-Id: Ie92dc368c502b9bc3fddef56a5eb0a238760f673 (cherry picked from commit 0a8380b)
Member
|
The changes in this PR have been included in Bazel 6.4.0 RC1. Please test out the release candidate and report any issues as soon as possible. If you're using Bazelisk, you can point to the latest RC by setting USE_BAZEL_VERSION=last_rc. |
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
7 participants
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.
In the following PR we extended most of the REv2 *Request messages to take an explicit digest function:
bazelbuild/remote-apis#235
This eliminates the ambiguity between digest functions that have the same hash length (e.g., MD5 and MURMUR3, SHA256 and SHA256TREE). This change extends the REv2 client in Bazel to set the digest_function field explicitly, so that the server does not need to use any heuristics to pick a digest function when processing requests.
As we are now going to call DigestUtil.getDigestFunction() far more
frequently, alter DigestUtil to precompute the value upon construction.
This change was tested by letting Bazel forward all traffic through an instance of bb_clientd that was patched up to require the use of
digest_function.