| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
|
Thanks for your pull request! It looks like this may be your first contribution to a Google open source project. Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA). View this failed invocation of the CLA check for more information. For the most up to date status, view the checks section at the bottom of the pull request. |
Sorry, something went wrong.
|
Hi @014-code, thank you for your contribution! We truly appreciate your work on this PR. I have noticed that your branch is currently out of sync with main and there are some issues with the Maven build with your changes. Could you please rebase your branch and resolve the build issues so we can proceed with the review process? |
Sorry, something went wrong.
Hi @hemasekhar-p, thanks for the feedback. I rebased the branch onto the latest main (d7355a71) and fixed the Maven build issue caused by using an unsupported RxJava Flowable.flatMapPublisher(...) operator. I also updated the asynchronous retry tests to wait for retry completion before asserting the terminal error. Validation performed:
The branch has been force-pushed as a single commit (b4a1a05e). This PR fixes #1397. |
Sorry, something went wrong.
|
Hi @014-code, thank you for the update. Our team is currently reviewing your PR and we will let you know if any further information is required. Thank you! |
Sorry, something went wrong.
| Back | FazBrowse Home | New Git URL |
Summary
Adds an opt-in retry policy for transient LLM provider failures.
The retry boundary is placed around BaseLlm.generateContent(...) inside
BaseLlmFlow, so failed provider attempts can be retried without replaying
Runner-level side effects such as user events, session updates, or tool calls.
Changes
Tests
Added coverage for:
google-java-format, git diff --check, and an independent javac
compilation of RetryConfig passed.
The full Maven test suite could not be executed in this environment because
the local Maven cache is missing a large number of project dependencies.
Fixes #1397