fix: Leading whitespace chunks break partial parser (structured outputs) #1213
+78
−1
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.
Changes being requested
Although
gpt-4o-mini-2024-07-18
in general supports structured outputs, we observed after integration that the model responds quite regularly with leading newline chunks (while the overall response is valid JSON)Since the partial parser does not allow (trimmed) empty strings – which is also reasonable – the only reasonable thing to handle such case is to handle this case before the parser is tried and default to a
null
value instead.Additional context & links
Example
Fingerprint:
fp_0705bf87c0
Request ID:
chatcmpl-Ab7XYB0hNxuJawO9gM0c4Doy0GTQP
Beginning of example output stream