| commit | cb2cd9fd2b65311da927777c35939701add5b879 | [log] [tgz] |
|---|---|---|
| author | Googler <larsrc@google.com> | Fri Jul 01 02:06:40 2022 -0700 |
| committer | Copybara-Service <copybara-worker@google.com> | Fri Jul 01 02:07:58 2022 -0700 |
| tree | 490cdef9479f3aea0ab965add9e360140f786277 | |
| parent | 7892749346a878af3d9a446c42f14f52e26b1788 [diff] |
Adds flag `--experimental_worker_strict_flagfiles` that checks if the worker argument list conforms to the spec. The spec calls for only one flag file, at the end of the argument list. However, the implementation allows for multiple flag files with startup arguments possible between or after. This has led to subtle bugs. We could also make the spec conform to the implementation, but there are fewer surprises possible with the spec, and it makes it much clearer that there is a distinction between startup args and per-request args. We would like to make it even more explicit, and possibly at the same time allow differing flags for workers and non-workers (e.g. for JIT/GC tweaking), but that would be a larger change. PiperOrigin-RevId: 458415814 Change-Id: I7eacfa7e6344348f66b6c83139c3bcd893bdd70b
{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
