-
Notifications
You must be signed in to change notification settings - Fork 233
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
The command crc status -w
on Windows writes out escape codes
#3936
Comments
@jeffmaury does it behave the same in the powershell window as well or this happens only in the windows terminal app? |
These are escape codes (that are not interpreted correctly. And as it looks like, you are running the command prompt I do not think this is a situation with a high priority, as |
@anjannath how about Mac? |
So it is the color. Perhaps a solution could be to make it all colorless or not for /cc: @evidolob WDYT? |
Yes we could do that, perhaps, even detect if terminal supports color, and add only if terminal supports colours |
It seems that Windows 10(from build 10586) does support colours in terminal, we need to enable it. @gbraad WDYT? |
https://github.com/crc-org/crc/blob/main/pkg/os/terminal/terminal.go provides support to check if we run in a terminal or not, this could be extended to check if color output is supported. |
/assign |
crc status -w
on Windows writes out escape codes
When I sent a The problem seems to be with the progressbar pool as I am not running into this when I am printing the progress bar independently. |
fixed in #3955 |
General information
crc setup
before starting it (Yes/No)? YesCRC version
CRC status
CRC config
- consent-telemetry : yes
Host Operating System
Steps to reproduce
Expected
Actual
Logs
Before gather the logs try following if that fix your issue
Please consider posting the output of
crc start --log-level debug
on http://gist.github.com/ and post the link in the issue.The text was updated successfully, but these errors were encountered: