commit | 0a93c1f731ae674afa5e0069e83d48900d9f2e98 | [log] [tgz] |
---|---|---|
author | jhorvitz <jhorvitz@google.com> | Wed Nov 24 13:06:41 2021 -0800 |
committer | Copybara-Service <copybara-worker@google.com> | Wed Nov 24 13:07:39 2021 -0800 |
tree | 7e1c12d157d53dc9266bb211533066e84124d4ca | |
parent | 3069ac4e33dcca6f3d1abf55940cdd764d03bdbf [diff] |
Enrich the Skyframe exception handling API with methods that promote code reuse and request batching. While refactoring `AspectFunction`, I've noticed that Skyframe requests may be suboptimally batched when different keys throw different exception types because the author probably felt that batching them introduced too much complexity. Another pattern I'm seeing is the use of helper functions which may expect only a certain exception type and/or arity of `ValueOrExceptionN`, leading to suboptimal batching to fit the method's requirements. An example is `ConfiguredTargetFunction#computeDependencies`, where aspects are not requested along with configured targets - requesting them together would make calling into the helper function `ConfiguredTargetFunction#resolveConfiguredTargetDependencies` difficult. The new methods in this change already have some use cases and will additionally allow me to batch configured target and aspect requests as mentioned above without introducing code duplication. PiperOrigin-RevId: 412120270
{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