tracing colors cannot be suppressed #65
Comments
|
I'm glad it's working well for you! That's awesome :) I didn't realize that tracing-subscriber had no way to turn off colors via environment variable. Sounds like the upstream issue has some activity so I think we could wait and see, and I'm happy to publish a release of bore when tracing is updated. |
devin-ai-integration bot
added a commit
to silasalberti/bore
that referenced
this issue
Dec 5, 2024
This update adds support for the NO_COLOR environment variable in tracing output, which allows suppressing ANSI color codes in log output. This is particularly useful when running bore as a Windows service. Fixes ekzhang#65
|
I had Devin investigate this and seems like it's now fixed upstream. It tested the version upgrade locally and I created a PR (#146): https://preview.devin.ai/sessions/2b78db994f0848bfbd2b181fc33dc044 |
ekzhang
pushed a commit
that referenced
this issue
Dec 5, 2024
This update adds support for the NO_COLOR environment variable in tracing output, which allows suppressing ANSI color codes in log output. This is particularly useful when running bore as a Windows service. Fixes #65 Co-authored-by: devin-ai-integration[bot] <158243242+devin-ai-integration[bot]@users.noreply.github.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I am running bore to expose local ports to a remote Windows server and it works quite well, thank you!
The only annoyance I have noticed that log/tracing colors do not seem to be able to be turned off, which make the log files look funny when for example wrapping bore in WinSW (for running as a Windows service).
I tried
NO_COLOR, that only affects the help colors; but that does not affect tracing: tokio-rs/tracing#2388.Opening this issue to make you aware of that so it could be fixed when there is a fix in tokio tracing. :)
The text was updated successfully, but these errors were encountered: