-
Notifications
You must be signed in to change notification settings - Fork 175
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
sensuctl tabular output looks terrible on some versions of Windows #2906
Comments
There was an issue with this fix. Reopening. |
It seems that Cobra doesn't allow for setting the output channel for normal output and errors independently. As a result, everything is sent to |
Requires spf13/cobra#822 |
We may want to add a test to ensure messages go to stdout/stderr correctly after fixing this so that we can avoid having to discover issues in QA. |
There are still some bugs in Cobra preventing us from fixing this at the moment. |
Waiting on spf13/cobra#894 to get merged. |
Still waiting on the cobra pr. |
The Cobra PR got approved last week! It's still not merged yet, but here's hoping it happens soon! |
I also wonder if #3782 would help here |
upstream issue fixed and shipped in cobra 1.1.0 |
@fguimond @amdprophet did any of the recent work we've done on sensuctl/cobra 🐍 address this? |
@calebhailey - the issue is still there using the regular Windows command line (dos or PowerShell), however it does work with the new Windows Terminal https://www.microsoft.com/en-ca/p/windows-terminal/9n0dx20hk701?rtc=1&activetab=pivot:overviewtab. |
We should be able to fix this now by upgrading the version of Cobra we depend on. |
Ok, great. Thanks for confirming. 👍 |
Expected Behavior
sensuctl tabular output should be easy for human operators to read
Current Behavior
sensuctl tabular output on certain versions/configurations of Windows prints "garbage characters"
Possible Solution
Detect terminal characteristics and adjust tabular output formatting accordingly
Steps to Reproduce (for bugs)
Context
Garbage characters -- what I believe are control characters which aren't understood by the terminal -- make the output hard to read, increasing operator burden.
Thus far this seems to be a problem primarily on Windows 10.
In my Windows Server 2016 Data Center VM it looks fine:
In a Windows 10 VM:
In a user's Windows 10 Powershell:
Same user's cmd terminal, also on Windows 10:
Your Environment
The text was updated successfully, but these errors were encountered: