| commit | ef457ae14302e22ba217acbe2016a2d7c9630020 | [log] [tgz] |
|---|---|---|
| author | Googler <wyv@google.com> | Fri Nov 10 09:39:21 2023 -0800 |
| committer | Copybara-Service <copybara-worker@google.com> | Fri Nov 10 09:40:59 2023 -0800 |
| tree | b993f628e71f6c6e4f61fb792f1ad7cd3258ddca | |
| parent | 04d81dbea8e29c7f3c9ed398512633d3e40364a0 [diff] |
Make `Label#toString` return `@@`-prefixed labels This change causes all labels in error messages, log output, Build Event Protocol, etc. to be prefixed with double-at (`@@`) if they are from non-main repos. This prevents cases where messages contain stuff like `the target @abc~1.0//:def is wrong` but the user can't do `bazel query @abc~1.0//:def` at all, since the actual target is `@@abc~1.0//:def`. This required more test changes than expected as there have been many places in the codebase where we compare labels using some sort of string form (for example, toolchain types as automatic exec groups). Fixes https://github.com/bazelbuild/bazel/issues/18543. RELNOTES[INC]: All labels in Bazel error messages, log output, Build Event Protocol, etc. are now prefixed with double-at (`@@`) instead of single-at (`@`) where applicable, to properly denote that they contain canonical repo names. PiperOrigin-RevId: 581287175 Change-Id: I1261ab14067bcf5d44cd140e5528b5da5916dc87
{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
