{Core} Always use UTF-8 for command metadata log file encoding#17996
Merged
{Core} Always use UTF-8 for command metadata log file encoding#17996
Conversation
Collaborator
|
Core |
evelyn-ys
approved these changes
May 7, 2021
Member
Author
|
/azp run |
|
Azure Pipelines successfully started running 2 pipeline(s). |
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.
Fix #17994
Adopt microsoft/knack#247
Context
On Windows with English as the system language (without UTC-8 enabled), the system encoding by default is
cp1252(Western Europe), and Python will usecp1252as the file encoding by default.Writing Unicode characters like
汉字to log file results in error:Change
This PR forces command metadata log files to use UTF-8 so that
az feedbackworks on non-UTF-8 systems as well.