Fix non-determinism in FeatureConfiguration requestedFeatures field by sorting it. This comes directly (through many layers of indirection) from BUILD files (the features= attribute) and the order doesn't matter for semantics or equality checks or interning but changes how FeaureConfiguration is serialized. This can result in non-determinism because the version that will be in the interning table is whichever of the equality group got created first. It would probably be theoretically possible to sort these somewhere further away, but this one has the advantage that the fact that the set is sorted is a "local" property. RELNOTES: None. PiperOrigin-RevId: 882401522 Change-Id: I776d251c03e75355ab436237d5d4b5c8dae804e4
{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.
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
