Move upload layout computation into UploadLayout, formerly SelectionPartition. Pure refactoring; no behavior change. FileOpNodeMemoizingLookup.computeLeafIdsAndUploadOrder produced two results from one walk: dense leaf IDs, computed by the private NodeGraphLayout, and the upload order, computed by SelectionPartition. Moves the method, its DenseLeafIdsAndUploadOrder result and NodeGraphLayout into SelectionPartition, so that the whole layout lives in one class and FileOpNodeMemoizingLookup goes back to only materializing nodes. Since the class now assigns leaf IDs as well as partitioning the selection, it is renamed to UploadLayout, and its test to UploadLayoutTest. - UploadLayout.computeLeafIdsAndUploadOrder is static and takes the lookup, whose isSkipped and resolvedNode become package-private. - The computeLeafIdsAndUploadOrder tests stay in FileOpNodeMemoizingLookupTest, which has the build fixture they need, and only change their call site. PiperOrigin-RevId: 1005947594 Change-Id: I596d781841be1ab599a6de8253fc1c60f0571e0e
{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
