Fix/protocol utf8 truncation#238
Open
amirmalekian wants to merge 4 commits into
Open
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Implement a
truncateUTF8Byteshelper function to ensure that stringtruncation occurs at valid UTF-8 rune boundaries. Previously, the
protocol truncated strings by byte index, which could result in
invalid UTF-8 sequences if a multi-byte character was split.
This change affects:
Replace naive byte-level slicing with
truncateUTF8Byteswhenencoding profile picture bundles. This prevents splitting multi-byte
characters at the 255-byte boundary, which previously caused
invalid UTF-8 sequences in the protocol.