feat: Retry-mechanism for rate-limit (google) #1322
+40
−11
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
hersche
force-pushed
the
main
branch
2 times, most recently
from
713767c to
9fc0212
Compare
added 2 commits
February 25, 2025 23:43
hersche
changed the title
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Hi there,
first a disclaimer: this was completely written by Goose/Gemini! Feel free to discard any changes and put a eye on it, as i am not much into Rust and had some headache while playing with this.
However, i have let my version with this change run and it was great, as it just continued with a small delay.
As the delay doubles after each try, it worked after the 3. try for me (2s, 4s, 8s -> total 14s delay) at least two times and then just finished it's task.
Besides how this feature is implemented, it would be a great one to have less frustrations because of aborts :)