Stream module lockfiles directly to disk (https://github.com/bazelbuild/bazel/pull/30428) ### Description Stream `MODULE.bazel.lock` serialization through a buffered UTF-8 writer instead of building the complete JSON as a `String`. The same helper writes both workspace and hidden lockfiles. Preserve the existing trailing newline and I/O failure logging, and add a regression test for the exact persisted JSON and newline. ### Motivation A real hidden lockfile reached 456,397,262 bytes (435.254 MiB). `Gson.toJson(updatedLockfile) + "\n"` creates two full strings, about 870 MiB of transient heap, and can fail in `BazelLockFileModule.updateLockfile` with `java.lang.OutOfMemoryError: Java heap space`. Streaming Gson directly to disk removes those full-size intermediate strings. ### Build API Changes No ### Checklist - [x] I have added tests for the new use cases (if any). - [x] I have updated the documentation (if applicable). ### Release Notes RELNOTES: None Closes #30428. PiperOrigin-RevId: 955067300 Change-Id: I637f7cb724101d197b6ec64e1eb3081717f7c8e4
{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
