turn off supervisor log coloring in local windows studio if ANSI is not supported #6306
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.
On Windows versions prior to 10.0.10586(TH2), the standard windows console did not understand ANSI code sequences. While we have adopted the
termcolor
crate to use console APIs instead of ANSI sequences on Windows,termcolor
will fall back to ansi if it cannot find a console. This will happen if habitat is running in a headless environment like a windows service or in a local studio where we launch it in the background.We already specify
--no-color
as a default parameter in thewindows-service
but the local studio should turn off color if runing in a older version of windows like 2012R2 or even an earlier 2016 build.This sniffs the OS version and adds
--no-color
and also setsHAB_NOCOLORING
on non ANSI supporting versions:BEFORE:
AFTER:
Signed-off-by: mwrock matt@mattwrock.com