aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorTiago Quelhas <tjgq@google.com>2024-02-15 20:15:09 +0100
committerGitHub <noreply@github.com>2024-02-15 20:15:09 +0100
commit9ff14cecffe5287ba337f857731ceadfc2d80de9 (patch)
treebbeb020b8b56cfcc8efd1f9678bf9d01748ba52b
parentd20ae8b97fd3330748e04660343964e6c8a13704 (diff)
downloadbazelbuild-remote-apis-9ff14cecffe5287ba337f857731ceadfc2d80de9.tar.gz
Clarify how Digest.hash is encoded generally (#285)
It seems bad form to special-case SHA-256 while not saying anything about other digest functions.
-rw-r--r--build/bazel/remote/execution/v2/remote_execution.proto4
1 files changed, 2 insertions, 2 deletions
diff --git a/build/bazel/remote/execution/v2/remote_execution.proto b/build/bazel/remote/execution/v2/remote_execution.proto
index 0bad5d1..1a01b7f 100644
--- a/build/bazel/remote/execution/v2/remote_execution.proto
+++ b/build/bazel/remote/execution/v2/remote_execution.proto
@@ -981,8 +981,8 @@ message SymlinkNode {
// serializing, but care should be taken to avoid shortcuts. For instance,
// concatenating two messages to merge them may produce duplicate fields.
message Digest {
- // The hash. In the case of SHA-256, it will always be a lowercase hex string
- // exactly 64 characters long.
+ // The hash, represented as a lowercase hexadecimal string, padded with
+ // leading zeroes up to the hash function length.
string hash = 1;
// The size of the blob, in bytes.