| commit | aa480481726efb5def0c1ce2a3e07584bf11b507 | [log] [tgz] |
|---|---|---|
| author | Googler <nharmata@google.com> | Mon May 20 10:02:40 2024 -0700 |
| committer | Copybara-Service <copybara-worker@google.com> | Mon May 20 10:04:17 2024 -0700 |
| tree | 2bae99e74ddc6c9a5d83550b8c9201aeb2d693b1 | |
| parent | 5cafcc45a1c88ab9c6e68caa8544f8d493717f0b [diff] |
Disable absl debug logging when `--client_debug=false` (the default). The Bazel client codebase doesn't use absl, but one of the library we use (e.g. gRPC) might. We wouldn't want that to spam the Bazel's user's stderr. Thus, this CL attempts to insulate the client program from that risk. We do this by disabling absl debug logging at the point in the life of the client program where we consider `--client_debug`. This is therefore a non-foolproof approach; consider a library we use that makes debug statements before that point in the life of our program. But we also add an integration test that would catch regressions like this! I noted future improvements in code comments. PiperOrigin-RevId: 635488965 Change-Id: I26d01f9aeda3a237aa68438586f958ae01d5448d
{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
