stdout color codes not recognized through Windows console anymore

[JPA2015]

When I start Martin v1.6.0 under Windows the stdout text in the console (cmd.exe) looks bad:

Apparently it contains color codes that don't get interpreted correctly anymore.

I can't say if it is new in this version or if it is already older. But I can remember using a version of Martin last summer and at this time the color were correctly displayed.

[CommanderStorm]

Can you try running us in the windows terminal or powershell instead?

cmd.exe is the legacy terminal, so the regular ansi escape codes that might not be well supported...

[JPA2015]

Thanks for your answer. The exact operating system is Windows Server 2019 Standard.
It looks the same with powershell (windows terminal is not available):

It looks the same with Martin v1.3.0:

The colors were correct with Martin v1.2.0:

If I start it on Windows 11 in windows terminal, the colors are correct with Martin v1.6.0.
So probably it is not so important, if it only happens on old OS.

[CommanderStorm]

cmd.exe was apprently deprecated as of 5y ago and the API that this specific termial requires to be called are not implemented currently.

https://www.reddit.com/r/rust/comments/l9ftyi/comment/glhut83/

The reason behind this is apparently that the amount of users for CMD is not that high anymore given this deprecation, so not a lot of motivation to fix this.
Likely if this were implemented, the tracing-subscriber crate would be open to a PR to fix ansi support.

Therer are two issues for this:

• Unable to output ANSI logs correctly in Windows powershell tokio-rs/tracing#2521
• ANSI color not working on CMD/Powershell but working on Terminal APP tokio-rs/tracing#3384

I think given that it works on modern windows versions, that would be a wontfix for me (also having to install windows 2019 for this is not very motivating..).
I would recomend updating your server to the latest version if windows 11 fixes this.

[JPA2015]

It is just, that it used to work. So it looks like as if something got broken.
This server is anyway just a test computer and the bug isn't blocking, it just makes the console more difficult to read.
"wontfix" is ok for me.
Thanks for taking the time to look at it.

[CommanderStorm]

It is a bug, but not one that I will realistically fix -> wontfix
The bug is in one of our dependencys and should be fairly simple to fix if you want to look into this 😉

In 1.3.0 we migrated to a more flexible logging framework.
You can now speifiy a few logging variants via the RUST_LOG_FORMAT environment variable.
Also, this allowed us to change the martin-cp logging to be actually good, not just meh.

Maybe you want to use the "bare" or "json" format instead? They don't use color I think.

[JPA2015]

Thanks for the trick with RUST_LOG_FORMAT: it's a good workaround.