| commit | de196ab1b1f42de7e059e6226cc7c65b724a8c9f | [log] [tgz] |
|---|---|---|
| author | Benjamin Peterson <benjamin@engflow.com> | Mon Jun 13 05:55:16 2022 -0700 |
| committer | Copybara-Service <copybara-worker@google.com> | Mon Jun 13 05:57:05 2022 -0700 |
| tree | 2041accdcb5d22ad04c6654933b22aba7f2e0dda | |
| parent | d7eaa0b63fee7a2878a8cc78f780bda5f59e1c96 [diff] |
Restructure blob upload code. The previous blob upload code had a lot of nesting and state shared between Future callbacks that made it hard to follow and modify. There is some fundamental complexity in the problem this code is solving; namely, retrying uploads can resume from the last comitted offset rather than always the beginning of the blob. I hope my rewrite makes the code easier to understand and paves the way for some future behavior modifications I want to make in this area. Closes #15514. PiperOrigin-RevId: 454588429 Change-Id: I9bc9c6942534053f19368fe4240dfe074ce8e60d
{Fast, Correct} - Choose two
Build and test software of any size, quickly and reliably.
Speed up your builds and tests: Bazel rebuilds only what is necessary. With advanced local and distributed caching, optimized dependency analysis and parallel execution, you get fast and incremental builds.
One tool, multiple languages: Build and test Java, C++, Android, iOS, Go, and a wide variety of other language platforms. Bazel runs on Windows, macOS, and Linux.
Scalable: Bazel helps you scale your organization, codebase, and continuous integration solution. It handles codebases of any size, in multiple repositories or a huge monorepo.
Extensible to your needs: Easily add support for new languages and platforms with Bazel's familiar extension language. Share and re-use language rules written by the growing Bazel community.
Follow our tutorials:
To report a security issue, please email security@bazel.build with a description of the issue, the steps you took to create the issue, affected versions, and, if known, mitigations for the issue. Our vulnerability management team will respond within 3 working days of your email. If the issue is confirmed as a vulnerability, we will open a Security Advisory. This project follows a 90 day disclosure timeline.
See CONTRIBUTING.md
