Fix color code detection in OutputManager #2430
Open
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.
Fixes #2341
This was a simple case of a mistaken translation from shell escape codes (which support octal
\NNN
) to C# (which only supports hex\xNN
and\uNNNN
in string literals, but does support octal\NNN
inRegex
). The test was passing because it also used incorrect escape codes, which matched the incorrect prefix.Edit: manual testing against the original repro repo: https://github.com/ian-h-chamberlain/actions-color-repro/actions/runs/4157866967