fix(program-log): avoid panic on invalid UTF-8 in host logger - #885
Open
raushan728 wants to merge 2 commits into
Open
fix(program-log): avoid panic on invalid UTF-8 in host logger#885raushan728 wants to merge 2 commits into
raushan728 wants to merge 2 commits into
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.
The host
stdlogging path unconditionally calledfrom_utf8(message).unwrap(), panicking on non-UTF-8 byte buffers, while the on-chain path passes raw bytes tosol_log_with no validation causing a host-only crash for callers that log byte buffers rather thanstr. Switched the host path toString::from_utf8_lossy.