| commit | 8850e931eb654428ca618a89fb912fd36213e3d9 | [log] [tgz] |
|---|---|---|
| author | Googler <lberki@google.com> | Fri Oct 21 01:56:59 2022 -0700 |
| committer | Copybara-Service <copybara-worker@google.com> | Fri Oct 21 01:57:58 2022 -0700 |
| tree | e6801faebf16a530eecfc1886afd327a6e0af5f0 | |
| parent | 491daafb11e73e0da1a77571e03b10cb0d8ac2e0 [diff] |
Keep the default value of option fields for which parsing failed. Before, they were set to null and I'm fairly certain it was not intentional: `OptionsParserImpl.getParsedOptions()` only checked whether the option has a value, but not if parsing for it succeeded. Then, if parsing failed, `OptionValueDescription.effectiveValue` remained unset, thus yielding null as the value of the option. This caused an actual bug with `--remote_download_outputs` . Even more confusing was that due to another, unrelated bug, the stack trace was not printed on the standard error, Bazel simply exited with the "internal error" exit code. RELNOTES: None. PiperOrigin-RevId: 482723418 Change-Id: Ia31fb344f48a3fb02aba7bdf9952c61b21672353
{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
