Closed jeffmaury closed 8 months ago
@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 cmd
instead of powershell.
I do not think this is a situation with a high priority, as crc status
works otherwise perfectly.
@anjannath how about Mac?
in macOS its fine, escape codes are being rendered properly..
So it is the color. Perhaps a solution could be to make it all colorless or not for GOOS=Windows
/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. We could use https://github.com/jwalton/go-supportscolor to add detection of color support on any supported OS, lib will also enable color support on windows.
@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.
@evidolob add a check to see if color support is available. We can otherwise use an override structure with _windows.go
if not working as expected.
Note: this is low priority and perhaps something @vyasgun can do?
/assign
When I sent a ctrl-c
after the bars start printing, I could see the expected output:
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
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.