bazel: Fix a `genrule()` crash when `srcs` have different depset order This crash was introduced by https://github.com/bazelbuild/bazel/commit/6baebe710147d1d1e0003cfe7490c259b7a15c38 which switched the code away from explicit `NestedSetBuilder.stableOrder()`. Unfortunately, the replacement `NestedSetBuilder.fromNestedSets()` call always uses the order of the first `NestedSet` as the order of the merged set. This means that a `genrule()` whose `srcs` have different depset order will crash with an error about incompatible ordering. To fix it, let's switch back to `.stableOrder()`, which allows multiple depsets with different order to be combined. PiperOrigin-RevId: 501424644 Change-Id: I4ea322993215d42850f05d389bda20c1b0f0feb4
{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
