Memoize ServerCapabilities in ReferenceCountedChannel to prevent connection pool exhaustion. ReferenceCountedChannel.getServerCapabilities() previously acquired a connection lease from DynamicConnectionPool on every invocation. When multiple Skyframe threads perform concurrent action cache checks (such as through CombinedCache), competing for connection leases leads to pool exhaustion, latency spikes, and potential deadlocks. Memoize the ServerCapabilities result in ReferenceCountedChannel so the connection lease and capability query occur at most once per channel lifetime. Speculatively fixes https://github.com/bazelbuild/bazel/issues/25308 PiperOrigin-RevId: 970533672 Change-Id: I14f5076c6b6863b6674e55cfc733db21aa549a9d
{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
