Split the gRPC and non-gRPC parts of GrpcServerImpl into separate classes. This makes it possible for a followup to move GrpcCommandServerImpl into the service component, while keeping CommandServer in the logic component (with GrpcCommandServer as the interface between them). There are some improvements yet to be made around exception handling in GrpcCommandServer.Responder (see comment in GrpcCommandServerImpl.BlockingStreamObserver) but I want to do them separately, as they entail some breakage risk. PiperOrigin-RevId: 885212357
{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
