fix: multi-byte character corruption when converting Buffers to strings #3100
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.
Description
This PR addresses corruption of multi-byte characters when those characters span across two chunks during decoding.
This problem is described in issue #2993 and @msebire provided a fix (and test cases) back in July in this comment. This PR incorporates those fixes.
NOTE: I searched for previous PRs for this issue (thinking that @msebire may have made one themselves), but couldn't find any.
Checklist
npm test
pass with this change (including linting)?