Fix OpenAI Responses chats stuck after SSE error events#559
Open
rschmukler wants to merge 1 commit into
Open
Conversation
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.
Summary
Handle terminal SSE
errorevents from the OpenAI Responses API and route them through ECA's existing error and retry handling.Problem
An OpenAI Responses request can return HTTP 200 but terminate with an SSE error instead of
response.completed, for example:errorserver_is_overloadedECA previously handled
response.failed, but generic SSEerrorevents were passed to the stream callback and ignored. When the stream then closed normally, ECA emitted neither an error nor a finish event, leaving the chat marked as active indefinitely.Changes
errorevents as terminal OpenAI Responses errors.server_is_overloadedas a retryable provider overload.error.server_is_overloadedclassification.Verification
35 tests passed.
197 assertions passed.
No test failures.
No new
clj-kondoerrors.Editor diagnostics are clean.
I added a entry in changelog under unreleased section.
This is not an AI slop.