Fix crash when --package_path contains only non-existent directories When `--package_path` is set to directories that do not exist (e.g. `--package_path=/notadir`), `PathPackageLocator` previously skipped all missing entries and returned an instance with an empty list of path entries. Subsequent subsystems expecting at least one package path root (such as Skyfocus, execution tooling, and external package helpers) crashed with unhandled runtime exceptions (`NoSuchElementException` or `IndexOutOfBoundsException`). Validation now ensures `resolvedPaths` is not empty during package locator creation. If no directories exist on disk, Bazel fails fast with an `AbruptExitException` (`FailureDetails.PackageOptions.Code.PACKAGE_PATH_INVALID`, exit code 2) and reports a descriptive error: ``` ERROR: None of the directories specified in --package_path '/notadir' exist ``` Early initialization errors during `workspace.initCommand(...)` are caught and surfaced cleanly by `BlazeCommandDispatcher`. Fixes https://github.com/bazelbuild/bazel/issues/17774 PiperOrigin-RevId: 972049409 Change-Id: I311bdc07b65b2cb9912312d81dfd7dc6e8309692
{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
