Get desktop application:
View/edit binary Protocol Buffers messages
/ Same as build.bazel.remote.execution.v2.BatchReadBlobsResponse, / but without the data field, and add a `data_len` field.
Used in:
Used in:
Override/new field to track the length of the data.
Using 15 to stay at 1 byte, but higher than 3.
/ Same as build.bazel.remote.execution.v2.BatchUpdateBlobsRequest, / but without the data field, and add a `data_len` field.
Used in:
Used in:
Override/new field to track the length of the data.
Using 15 to stay at 1 byte, but higher than 3.
/ Bep event that has occurred.
/ The version of this message.
/ The identity header that generated the event. This will be populated / with the header value keyed by the specified by the / `IdentityHeaderSpec::header_name`.
/ The event that occurred.
Used in:
/ Nativelink event that has occurred.
Used in:
/ The version of this message.
/ The event UUIDv6. This is a unique identifier for the event for the / server that generated the event. / Note: The timestamp of when the event occurred is encoded in the UUID.
/ [optional] The parent event UUID. This is used to track the / parent event that generated this event. This is useful for / tracking the flow of events.
/ If the client is bazel, this is the meatadata that was sent with the / request. This is useful for tracking the flow of events.
/ The identity header that generated the event. This will be populated with / the value of the specified by the `IdentityHeaderSpec::header_name`.
/ The event that occurred.
/ Batch of events that have occurred.
Used in:
Used in:
Used in:
/ Same as google.bytestream.WriteRequest, but without the data field, / and add a `data_len` field.
Used in:
Override/new field to track the length of the data.
Using 15 to stay at 1 byte, but higher than 3.