[FIX] Handle non-UTF-8 output from subprocess tools#298
Draft
Mirochill wants to merge 1 commit into
Draft
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
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.
This PR...
UnicodeDecodeErrorwhen external map tooling writes non-UTF-8 bytes to stdout or stderr.Considerations and implementations
run_subprocess_and_log_output()keeps decoding subprocess output as UTF-8, but now passeserrors="backslashreplace"tosubprocess.run(). This prevents bytes such as0xa0from raising while still making undecodable bytes visible in the captured log output.Closes #271
How to test
git diff --checkgit show --check --stat --oneline HEADPull Request Checklist