Fix SimpleLogHandler log rotation/size-cap property names (https://github.com/bazelbuild/bazel/pull/30235) The server JVM logging config passed 'limit' and 'total_limit' keys, which are FileHandler property names left over from before the switch to SimpleLogHandler (commit 8b99432877). SimpleLogHandler (commit 172d36dfe19) reads 'rotate_limit_bytes' and 'total_limit_bytes', so both values fell back to 0 (unlimited): java.log never rotated and the 20 MB total cap was never enforced. The dead rotate branch also disabled the only per-record flush, leaving the log tail buffered in memory. ### Description this rewires properties that got lost in commit 8b99432877. ### Motivation this leaves log records in memory for longer, which makes debugging crashes harder. ### Build API Changes n/a ### Checklist - [ ] I have added tests for the new use cases (if any). - [ ] I have updated the documentation (if applicable). ### Release Notes RELNOTES: None Closes #30235. PiperOrigin-RevId: 967036476 Change-Id: Ie7eca5364e71e49ccfded4bdeb8051947f79b2d0
{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
