fix: keep conversation titles valid UTF-8 in promptToTitle truncation - #9837
Open
eminemead wants to merge 1 commit into
Open
fix: keep conversation titles valid UTF-8 in promptToTitle truncation#9837eminemead wants to merge 1 commit into
promptToTitle truncation#9837eminemead wants to merge 1 commit into
Conversation
Byte-wise title[:47] split multi-byte Chinese runes, so ListConversations could not marshal existing sessions.
nishantmonu51
added
Type:Bug
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
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.
ListConversationsfailed to marshal when a stored conversation title contained invalid UTF-8.promptToTitletruncated with a byte slice (title[:47]), which split multi-byte runes.strings.ToValidUTF8at the marshal boundary (invalid bytes become U+FFFD) so previously stored rows still list.Checklist:
Developed in collaboration with Claude Code