Closed gejohnston closed 4 months ago
Thank you for creating a bug report. We will investigate the bug and evaluate its impact on the product. If you haven't already, please ensure you have provided steps to reproduce the bug and as much context as possible.
I'm seeing different behavior on Linux and Windows. With version 8.0.0-next.202402261705 from npm, in Windows Powershell I still see a progress bar, on Linux (MX Linux using Konsole) the progress bar is not shown.
I'm not running in daemon mode and neither FORCE_COLOR nor CI environment variables are set.
Actually, I lose colors on Linux when running vnext.
(edit, I had FORCE_COLOR set to 1 in my .zowe.env.json on Windows, removing the variable causes colors and progress bars to not be shown)
With Zowe 8.0.0-next.202402261705, Windows never displays a progress bar for me. I tried the native Powershell terminal with Powershell version 5.1.19041.3930. I also tried Powershell version 7.4.1 in a native Powershell terminal and also within ConEmu.
I saw Zowe V2 display a progress bar in both Windows and Linux. Zowe 8.0.0-next.202402261705 does not display the progress bar for me in either Windows or Linux.
I have confirmed I broke this with the dependency upgrades. Chalk removed the .enabled
property, and I thought I fixed this, but the change may have been on my branch that broke so spectacularly that I started over. I am opening a PR momentarily to fix this behavior.
We also may need to warn extenders who were using that property, because we were exporting Chalk in TextUtils for ease of use.
Describe the bug
Progress bars do not display on long running commands. This occurs on Windows and Linux.
Expected and actual results
The following command displayed no progress bar. It takes a few seconds and I would have expected a progress bar.
Describe your environment
Also, the
zowe config report-env
command always displays a progress bar while gathering NPM information (it is a slow process). Thereport-env
command displays no progress bar in vNext.Additional context