Repository navigation
Decode the LLM event stream as UTF-8 - #11
Merged
Merged
Conversation
Groq's event stream carries no charset, so requests decoded it as ISO-8859-1 and streamed answers showed mojibake (for example around µmol/kg and narrow spaces). Read bytes and decode each line as UTF-8. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
|
Important
This repository does not receive automatic reviews because it has fewer than 10 stars.
 |
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.
Streamed answers from
/query/streamshowed mojibake, for example0.8 µmol/kginstead of0.8 µmol/kg. Groq's event stream has no charset in itsContent-Type, sorequestsdecoded it as ISO-8859-1. The fix reads the stream as bytes and decodes each line as UTF-8; a unit test covers it.This only affected streaming.
/queryuseschat(), which decodes JSON correctly. But both endpoints share the answer cache, so a garbled streamed answer could also be served by/query. The redeploy clears that in-memory cache.Found while building the Phase 3 web app, the first client of the streaming endpoint.
🤖 Generated with Claude Code