commit | 6d79e11a15e59b6d2ef6838efe780f7c0b820387 | [log] [tgz] |
---|---|---|
author | George Gensure <ggensure@lat.ai> | Thu Apr 25 09:08:56 2024 -0700 |
committer | Copybara-Service <copybara-worker@google.com> | Thu Apr 25 09:10:47 2024 -0700 |
tree | 68f47cb24c0e7350579c46aa356d3c56c703fc4d | |
parent | 028c7c104d5acff79c4944281c2499129fecd11b [diff] |
Handle operation stream exception in wrapper A literal StatusRuntimeException thrown from a response stream iterator (as an error response to the overall request) should have the same consideration as one thrown from the operation response unwrap. waitExecution requires an additional check for SRE thrown directly from operation stream pop. Existing NOT_FOUNDs that do not pass the inner retry check will similarly be passed through. To detect this NOT_FOUND in test, the actual exception thrown as a result of thenError must be the error response from stream provided by FakeExecutionService. This corrects a number of tests which did not check for explicit exceptions and were relying on UNKNOWN SREs resulting from errors during handling, and removes numerous thenAck()s required to validate tests. Closes #22067. PiperOrigin-RevId: 628094669 Change-Id: I011d2c2321074a1a27dc853f6274ba9ef35f6db6
{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