fix(openai): handle missing 'text' key in responses API content blocks #34198
+38
−1
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
Add defensive check for missing 'text' key in text/output_text blocks
when constructing Responses API input. Blocks without 'text' key are
now skipped instead of raising KeyError.
- Add defensive check using block.get('text') for text/output_text blocks
- Skip blocks when text is None
- Add test case to verify blocks without text key are skipped
Fixes issue where block_type is 'text' or 'output_text' but block
dictionary lacks 'text' key, causing KeyError.
…ponses-api-composer-1-c756 Fix missing text key in responses api
github-actions
bot
added
integration
Member
|
Why would this ever be the case? What usage prompted this? |
Author
|
I found that when using the GPT-5.1 model, occasionally the first chunk of its response is [{ "type": "text", index: -1 }], but this happens very rarely. 
|
Member
|
Is this using the OpenAI API directly or wrapping via some proxy/router service? |
Author
|
OpenAI API directly |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
Fix KeyError when processing assistant message content blocks in
_construct_responses_api_inputfunction. The code was directly accessingblock["text"]without checking if the key exists, which could cause a KeyError when processing malformed or incomplete content blocks.This change adds defensive checks using
block.get("text")to safely handle cases where the "text" key might be missing from content blocks with type "text" or "output_text".