| commit | acc1ff6eaad9fffb40dbdada089052fa80a28b29 | [log] [tgz] |
|---|---|---|
| author | Xùdōng Yáng <wyverald@gmail.com> | Tue Aug 06 19:02:34 2024 -0400 |
| committer | GitHub <noreply@github.com> | Tue Aug 06 23:02:34 2024 +0000 |
| tree | 154d9dd9e5798a8fee1d2abd35f141508e8c6a08 | |
| parent | 5f5355b75c7c93fba1e15f6658f308953f4baf51 [diff] |
[7.3.0] Be resilient to outdated exec paths in action cache entries (#23230) https://github.com/bazelbuild/bazel/commit/60924fdc2972184494f6382d39e8c786aa14b9a9 changed the canonical repo name separator from `~` to `+`. Older repo names containing `~` now trigger a syntax error. If an action cache entry refers to an exec path from a previous version of Bazel that used `~`, we need to be resilient and treat the cache entry as corrupted, rather than just crash. Fixes https://github.com/bazelbuild/bazel/issues/23180. Closes #23227. PiperOrigin-RevId: 660105601 Change-Id: Iea5d86c635056d12ba20598383da463bdde03ab0
{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
