| commit | b95f0a7f0f9b0d8c361822a1badff2bb78919cd5 | [log] [tgz] |
|---|---|---|
| author | Googler <noreply@google.com> | Tue May 20 14:37:25 2025 -0700 |
| committer | Copybara-Service <copybara-worker@google.com> | Tue May 20 14:38:35 2025 -0700 |
| tree | f653722123d23d7f151be99ea405993616538b00 | |
| parent | b441c8c6f2a6fbc20eb0aa9e76451050b31c3904 [diff] |
LSC: Refactor Protobuf Message.toString calls that blocks[] [] In this case, the test can be fixed without modifying the toString() call by changing what is compared against. Background: Protobuf Message.toString() currently serializes all the fields in a proto into a human-readable representation, which has led to many privacy incidents where Message.toString() outputs containing sensitive fields (e.g. private keys) were accidentally logged. To prevent such privacy incidents, while minimizing reliability risks, we (orrery-debug-string@) are in the process of changing Protobuf Message.toString()’s output format in stages:[] PiperOrigin-RevId: 761235046 Change-Id: I26b6073aeea4eb6e6460f84c5084470798eeef9b
{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
