fix(vfs): preserve raw bytes when reading /dev/urandom#828
Merged
Conversation
Closes #811 — /dev/urandom now returns raw bytes instead of UTF-8 replacement characters. Changed file content conversion from String::from_utf8_lossy (which replaces bytes > 0x7F with U+FFFD) to Latin-1 mapping (each byte 0x00-0xFF maps to its Unicode code point).
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.
Summary
String::from_utf8_lossywith Latin-1 byte-to-char mapping for file readsTest plan
urandom_no_replacement_chars— verifies no U+FFFD in od outputCloses #811