Repository navigation
fix(agent): retry a rate limit reported mid-stream - #1141
Merged
Merged
Conversation
Pins aither at the commit that classifies a mid-stream rate_limit_exceeded as transient, so the turn retry handles it. Closes #1140
This file contains hidden or 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
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.
Pins aither at May-Agent/aither#776, which classifies a
rate_limit_exceededreported after a Responses stream started as transient instead of permanent, so May's turn retry handles it. The other aither change in range touches its release workflow. Lockfile only: the update also re-resolvedwindows-systo 0.61.2 for the Windows-only dependents oftempfile,rustix,socket2,curland similar, which the Windows builds cover.Closes #1140