You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
* Chunker: Always seek on the uncompressed stream.
The `WriteRequest.write_offset` field has bizarre semantics during compressed uploads as documented in the remote API protos: https://github.com/bazelbuild/remote-apis/blob/3b4b6402103539d66fcdd1a4d945f660742665ca/build/bazel/remote/execution/v2/remote_execution.proto#L241-L248 In particular, the write offset of the first `WriteRequest` refers to the offset in the uncompressed source.
This change ensures we always seek the uncompressed stream to the correct offset when starting an upload call. The old code could fail to resume compressed uploads under some conditions. The `progressiveCompressedUploadShouldWork` test purported to exercise this situation. The test, however, contained the same logic error as the code under test.
Closes#15669.
PiperOrigin-RevId: 455083727
Change-Id: Ie22dacf31f15644c7a83f49776e7a633d8bb4bca
* Updated chunker.java file.
* Update src/test/java/com/google/devtools/build/lib/remote/ByteStreamUploaderTest.java
Co-authored-by: Benjamin Peterson <[email protected]>
* Update src/test/java/com/google/devtools/build/lib/remote/ByteStreamUploaderTest.java
Co-authored-by: Benjamin Peterson <[email protected]>
* Update src/test/java/com/google/devtools/build/lib/remote/ByteStreamUploaderTest.java
Co-authored-by: Benjamin Peterson <[email protected]>
Co-authored-by: Benjamin Peterson <[email protected]>
Co-authored-by: Benjamin Peterson <[email protected]>
0 commit comments