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

"Response From Service" section may be confusing for non-REST errors #2345

Open
t1m0thyj opened this issue Nov 1, 2024 · 2 comments
Open
Labels
bug Something isn't working priority-low Legit issue but cosmetic or nice-to-have severity-low Bug that makes the usage of the Zowe less convenient but doesn't impact key use cases

Comments

@t1m0thyj
Copy link
Member

t1m0thyj commented Nov 1, 2024

The "Response From Service" section is helpful for diagnosing HTTP errors. For other types of errors it may present a duplicate message that is potentially misleading if the error is client-side and there was no response from the service, e.g.:

$ zowe zos-files upload file-to-uss doesNotExist.txt /u/users/timothy/usstest.txt
Unable to perform this operation due to the following problem.
Node.js File System API error

Response From Service
Error: ENOENT: no such file or directory, lstat 'doesNotExist.txt'

Diagnostic Information
Error: ENOENT: no such file or directory, lstat 'doesNotExist.txt'

A suggested fix would be to only populate this section when the error is handled by AbstractRestClient.populateError.

@t1m0thyj t1m0thyj added bug Something isn't working new The issue wasn't triaged yet labels Nov 1, 2024
@github-project-automation github-project-automation bot moved this to New Issues in Zowe CLI Squad Nov 1, 2024
Copy link

github-actions bot commented Nov 1, 2024

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.

@adam-wolfe
Copy link
Contributor

Loosely related to #2223

@JTonda JTonda added priority-low Legit issue but cosmetic or nice-to-have severity-low Bug that makes the usage of the Zowe less convenient but doesn't impact key use cases and removed new The issue wasn't triaged yet labels Nov 4, 2024
@zowe-robot zowe-robot moved this from New Issues to Low Priority in Zowe CLI Squad Nov 4, 2024
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-low Bug that makes the usage of the Zowe less convenient but doesn't impact key use cases
Projects
Status: Low Priority
Development

No branches or pull requests

3 participants