Merged
Conversation
Contributor
|
Wondering how you validated that this solves things? We should also link an issue to this PR so that it's clear what it's trying to fix. |
Contributor
Author
|
This one is actually already linked to an issue, to #6960. (Maybe the ZenHub way of linking stuff isn't preferable in this repo?) I did this to verify: With the patch, |
Contributor
|
Zenhub linking doesn't end up anywhere in the git history, which is why we usually prefer to mention the issue as part of the PR description so that it gets saved for posterity in the commit history. |
riarenas
approved these changes
Mar 3, 2021
Contributor
Author
|
/azp run |
|
Azure Pipelines successfully started running 1 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.
This is going to work with runtime's
dotnet.cmdafter adding something likechcp 65001to that script.If I understand the situation properly,
Set-Content -Encodingchanged defaults between different versions of PowerShell from "system's active code page" to "utf8NoBOM". It's probably better for us to fix that value more often than not.Solves #6960