Skip to content
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

zowe --available-commands fails with stack trace when running in daemon mode #2429

Open
adam-wolfe opened this issue Feb 6, 2025 · 1 comment
Labels
bug Something isn't working priority-low Legit issue but cosmetic or nice-to-have severity-medium Bug where workaround exists or that doesn't prevent the usage of Zowe. Just makes it more complex.

Comments

@adam-wolfe
Copy link
Contributor

adam-wolfe commented Feb 6, 2025

Describe the bug

If I am running Zowe CLI in daemon mode and run the zowe --available-commands command Zowe CLI fails with Unexpected Command Error and prints out a stack trace. No error is produced if not running in daemon mode.

The --available-commands flag works in daemon mode when not run at the root level (e.g., zowe files list --available commands).

Expected and actual results

Describe your environment

Zowe CLI v8.11.0
OS: Windows 10

Additional context

The error message and stack trace:

PS C:\> zowe --available-commands
Unexpected Command Error:
Please review the message and stack below.
Contact the creator of handler:
"C:\Users\me\AppData\Roaming\npm\node_modules\@zowe\cli\node_modules\@zowe\imperative\lib\imperative\src/handlers/DefaultRootCommandHandler"
Message:
TextUtils_1.TextUtils.chalk[ImperativeConfig_1.ImperativeConfig.instance.loadedConfig.primaryTextColor] is not a function
Stack:
TypeError: TextUtils_1.TextUtils.chalk[ImperativeConfig_1.ImperativeConfig.instance.loadedConfig.primaryTextColor] is not a function
    at Imperative.highlightWithPrimaryColor (C:\Users\me\AppData\Roaming\npm\node_modules\@zowe\cli\node_modules\@zowe\imperative\lib\imperative\src\Imperative.js:355:119)
    at C:\Users\me\AppData\Roaming\npm\node_modules\@zowe\cli\node_modules\@zowe\imperative\lib\imperative\src\handlers\DefaultRootCommandHandler.js:52:77
    at Array.forEach (<anonymous>)
    at DefaultRootCommandHandler.<anonymous> (C:\Users\me\AppData\Roaming\npm\node_modules\@zowe\cli\node_modules\@zowe\imperative\lib\imperative\src\handlers\DefaultRootCommandHandler.js:50:25)
    at Generator.next (<anonymous>)
    at C:\Users\me\AppData\Roaming\npm\node_modules\@zowe\cli\node_modules\@zowe\imperative\lib\imperative\src\handlers\DefaultRootCommandHandler.js:18:71
    at new Promise (<anonymous>)
    at __awaiter (C:\Users\me\AppData\Roaming\npm\node_modules\@zowe\cli\node_modules\@zowe\imperative\lib\imperative\src\handlers\DefaultRootCommandHandler.js:14:12)
    at DefaultRootCommandHandler.process (C:\Users\me\AppData\Roaming\npm\node_modules\@zowe\cli\node_modules\@zowe\imperative\lib\imperative\src\handlers\DefaultRootCommandHandler.js:33:16)
    at CommandProcessor.<anonymous> (C:\Users\me\AppData\Roaming\npm\node_modules\@zowe\cli\node_modules\@zowe\imperative\lib\cmd\src\CommandProcessor.js:465:39)
@adam-wolfe adam-wolfe added bug Something isn't working new The issue wasn't triaged yet labels Feb 6, 2025
@github-project-automation github-project-automation bot moved this to New Issues in Zowe CLI Squad Feb 6, 2025
Copy link

github-actions bot commented Feb 6, 2025

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.

@JTonda JTonda added priority-low Legit issue but cosmetic or nice-to-have severity-medium Bug where workaround exists or that doesn't prevent the usage of Zowe. Just makes it more complex. and removed new The issue wasn't triaged yet labels Feb 10, 2025
@zowe-robot zowe-robot moved this from New Issues to Low Priority in Zowe CLI Squad Feb 10, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working priority-low Legit issue but cosmetic or nice-to-have severity-medium Bug where workaround exists or that doesn't prevent the usage of Zowe. Just makes it more complex.
Projects
Status: Low Priority
Development

No branches or pull requests

2 participants