Skip to content

fix(example): derive streaming response parser boundaries from schema#2287

Merged
abetlen merged 1 commit into
mainfrom
fix/schema-driven-stream-parser
Jun 8, 2026
Merged

fix(example): derive streaming response parser boundaries from schema#2287
abetlen merged 1 commit into
mainfrom
fix/schema-driven-stream-parser

Conversation

@abetlen

@abetlen abetlen commented Jun 8, 2026

Copy link
Copy Markdown
Owner

Fix streaming response parsing for schema-defined chat markers.

  • Derives assistant prefixes, reasoning spans, and stop markers from response_schema regex structure instead of hardcoded conversation tags.
  • Keeps terminal streaming chunks on the incremental parser path so incomplete reasoning spans do not leak raw markers.
  • Validated with parser smoke checks plus Qwen and Gemma endpoint smoke tests for chat, reasoning, tool calls, and Responses streaming.

@abetlen abetlen force-pushed the fix/schema-driven-stream-parser branch from 32dcf85 to 6f68536 Compare June 8, 2026 03:27
@abetlen abetlen changed the title fix: derive streaming response parser boundaries from schema fix(example): derive streaming response parser boundaries from schema Jun 8, 2026
@abetlen abetlen merged commit 411e0f4 into main Jun 8, 2026
15 checks passed
@abetlen abetlen deleted the fix/schema-driven-stream-parser branch June 8, 2026 03:29
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant