Skip to content

Valid entries returned by fetchFileAtUri in UssFSProvider for files that do not exist #3894

@t1m0thyj

Description

@t1m0thyj

Similar to #3252 which was for Data Sets, but this issue is for the USS tree - if I attempt to open a file and the getContents() call throws an error for some reason, then a blank file is opened in the editor and no error message is displayed.

Steps to Reproduce
An easy way to reproduce this without using an extender is to modify the implementation of ZoweExplorerZosmf.UssApi.getContents to throw an error.

Actual Behavior
If I attempt to open a file and the getContents() call throws an error for some reason, then a blank file is opened in the editor and no error message is displayed.

Expected Behavior
I would expect an error to be shown to match the behavior for data sets:
Image

Metadata

Metadata

Assignees

Labels

bugSomething isn't workingpriority-highProduction outage - this quarter or at least next quarterseverity-highBug for which there may be workaround but limits the usage of the Zowe for major use cases

Type

No type
No fields configured for issues without a type.

Projects

Status
Closed

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions