| commit | 525df32b5dc60448e1abcd3d537ed3454a841946 | [log] [tgz] |
|---|---|---|
| author | Googler <jhorvitz@google.com> | Wed Jun 29 08:31:38 2022 -0700 |
| committer | Copybara-Service <copybara-worker@google.com> | Wed Jun 29 08:33:04 2022 -0700 |
| tree | 645d908ac24ba9e399560f8a90ce0bfb87a2f1f4 | |
| parent | 632af2cfe1d51609680cb02c28bf4557908b85ec [diff] |
Replace `ProgressLike` marker interface with a boolean method `storeForReplay`. Makes `Postable` instances not stored by default. In the common case, a post represents some sort of progress event, and storing it in skyframe is a waste of memory. All existing `Postable`-but-not-`ProgressLike` classes which are posted from a `SkyFunction` (as detected by running presubmit tests) are made to return true from `storeForReplay`. It is possible that some of these were unintentionally stored via the default behavior, but I will audit those in a followup. PiperOrigin-RevId: 457983032 Change-Id: I6c69b3907c20e3dac362f0c6a9610af17fc4d35d
{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
