fix(opencode): retry raw network finish errors - #43813
Merged
Merged
Conversation
opencode-agent
Bot
changed the title
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
1 participant
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.
Summary
finish-step.rawFinishReasondirectly in the existing adapternetwork_errorinto the existing retryable response-stream errorWhy this shape
AI SDK already preserves the provider value on
finish-step; handling it in the existing adapter avoids raw-chunk parsing and avoids adding stream middleware.Testing
bun test test/session/llm.test.ts --test-name-pattern "network_error finish reasons"bun test test/session/processor-effect.test.ts --test-name-pattern "retry network_error finish reasons"bun test test/session/retry.test.tsbun x prettier --check src/session/llm/ai-sdk.ts test/session/llm.test.ts test/session/processor-effect.test.tsRequested by: @rekram1-node (Aiden via Slack)