Fix: display Chinese characters correctly in conversation logs #3532
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
|
|
…ng ensure_ascii=False
d543046 to
f8686f4
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 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.
closes #3531
This patch adds ensure_ascii=False to the json.dumps call in _format_conversation to correctly display Chinese (and other Unicode) characters in the saved conversation logs.
Summary by cubic
Conversation logs now show Chinese and other Unicode characters correctly by setting ensure_ascii=False when dumping the response JSON. Fixes #3531.
Written for commit f8686f4. Summary will update automatically on new commits.