| commit | ac8930de1d5bae71bd0bf702a197d425ddc95f92 | [log] [tgz] |
|---|---|---|
| author | Googler <jhorvitz@google.com> | Tue Feb 14 12:28:03 2023 -0800 |
| committer | Copybara-Service <copybara-worker@google.com> | Tue Feb 14 12:31:16 2023 -0800 |
| tree | b827acd7ea2957852a173cc2cc99e47b42124d4e | |
| parent | d9795a7c28833a2a43084418b329bf032fa4bad2 [diff] |
Prevent arbitrary modifications to the backing `InMemoryGraph` map by removing the `getAllValuesMutable()` method in favor of more specific methods that don't expose a mutable map. The primary use case for exposing the graph as a `ConcurrentHashMap` is for the parallel `forEach` method. However, that is now implemented directly on `InMemoryGraph` as `parallelForEach`. The motivation for this change is for upcoming work on using `InMemoryGraph` as a `SkyKeyPool`, in which the `remove()` method will need to do some additional work to ensure weak interning of keys when they are removed from the pool. This change ensures that the only way to remove keys from the graph is to go through `InMemoryGraph#remove`. PiperOrigin-RevId: 509605561 Change-Id: I7ec69aeb58c26fa3e17f757fc357514f58480c1e
{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
