Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Adjust script/extract_log to handle non-utf8 sequences. #2124

Merged
merged 1 commit into from
May 1, 2024

Conversation

pellaea
Copy link
Member

@pellaea pellaea commented May 1, 2024

The "real" problem is why are there non-utf8 sequences in the log??? But be that as it may, code should never crash, as a general rule, and I can at least fix that...

@pellaea pellaea merged commit 40c4cd3 into main May 1, 2024
3 of 4 checks passed
@coveralls
Copy link
Collaborator

Coverage Status

coverage: 94.446%. remained the same
when pulling 7708bd3 on protect-extract-log-from-non-utf8
into 666f0c4 on main.

@mo-nathan
Copy link
Member

Thanks for fixing this. Given all the monkeys banging on all the keyboards, I can see non-utf8 sequences ending up in the log. I can specifically imagine monkeys with bad intent throwing binary data where it shouldn't go.

@pellaea
Copy link
Member Author

pellaea commented May 2, 2024 via email

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants