| commit | d8613c222f233406165c623b1a92179faed142ba | [log] [tgz] |
|---|---|---|
| author | Fabian Meumertzheim <fabian@meumertzhe.im> | Mon Apr 22 08:07:55 2024 -0700 |
| committer | Copybara-Service <copybara-worker@google.com> | Mon Apr 22 08:09:45 2024 -0700 |
| tree | 1431cac7b1187e2ebc125979c1785990e13ba042 | |
| parent | f2eec38c299fa71e58e21ab1d8b5094f1078e53b [diff] |
Fix action key staleness for Args due to type confusion When a command line item is subject to special default stringification behavior (currently, `Label` and `File` instances are), it does not suffice to fingerprint the information that computes the custom stringification; it is also necessary to track whether each individual item is subject to this special formatting. Otherwise, as demonstrated by numerous new test cases, command line items have identical fingerprints to their naive stringification, but may result in distinct command lines. This is fixed by tracking element types via additional UUID markers, either individually or for entire `NestedSet`s based on the `Depset` type. Closes #21999. PiperOrigin-RevId: 627040284 Change-Id: Id0725e7d7a58b439fde4f6644de09ebedb56a14c
{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
