| commit | b74b7cf3cb253ab268d1c5b7e6e9513a5bbad845 | [log] [tgz] |
|---|---|---|
| author | Googler <noreply@google.com> | Wed Sep 11 23:30:14 2024 -0700 |
| committer | Copybara-Service <copybara-worker@google.com> | Wed Sep 11 23:32:09 2024 -0700 |
| tree | c8903806621d3c7af0b57a8eb33bd1d1aa406e8e | |
| parent | a1fd39d15985b7b263a37945e232c1af2532bf6a [diff] |
Modify rc file parsing to allow for non-local files At present, rc file parsing assumes that all files are accessible via normal kernel file interfaces. This is a reasonable assumption, since files are either present on local disk or made available via a FUSE daemon. However, if we want to parse rc files which are only accessible via an RPC interface, this assumption breaks. While it is possible for the caller to download the root rc file from the remote location onto disk, the caller does not know the location of any child rcs referenced by the root rc file. Therefore, the only code capable of downloading these files is the parser itself. To resolve this, I have added two functors to `RcFile::Parse`, which by default indirect the local file operations, ensuring local parsing continues to work for existing callers. Callers that need different behavior can pass their own functors, which can make arbitrary RPCs as necessary. PiperOrigin-RevId: 673696308 Change-Id: Id820d43ce1d897e9da6b2cd4ab274809adbe7ba0
{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
