fix(openai): remove cumulative SSE event limits - #17
Merged
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
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
Allow OpenAI Responses streams to exceed the configured item cardinality in raw SSE and normalized event traffic. Collection sizes, response indexes, text fields, and wire bytes remain bounded.
Motivation
Pathological but valid responses can exceed 100,000 SSE events. Treating that count as a protocol violation currently terminates the model turn with a fatal provider error.
Impact
Large event streams can continue to their provider-supplied terminal event instead of failing at an arbitrary cumulative event count. Per-attempt and aggregate response byte limits remain the resource-safety boundary.
Technical details
Separate item cardinality from event traffic
max_itemscontinues to limit request and response collection cardinality and acts as the exclusive response-index bound. Raw SSE events and normalized model events no longer consume that budget.