Skip to content

Stuck on filtering non-existant USS path after submit #3449

Open
@JWaters02

Description

Describe the bug

Sorry for the title, not sure how to put it in a few words.

When I enter a non-existant path into the USS filter, as expected the error appears to say path name not found.

However, when clicking the filter button again to enter a new path, the error appears twice more, because it is still trying to filter on the non-existant path.

Also, I don't know if this is a seperate bug or intentional, but when I enter to filter on dataset or jobs profile, it also refreshes the USS filter, so the error still comes up.

Image

To Reproduce

Steps to reproduce the behavior:

  1. On USS profile, enter invalid path into filter and submit it
  2. See error that path name not found
  3. Click filter on USS profile again
  4. See same error that path name not found, x2

Expected behavior

I expect that when I get a path name not found error, the filter that I entered is "removed" (not from history, but from what it is trying to currently filter on).

Screenshots

Desktop (please complete the following information):

  • OS: Windows 10
  • Zowe Explorer Version: 3.1.0
  • (Optional) Zowe CLI Version:
  • (Optional) Are you using Secure Credential Store?

Additional context

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't workingpriority-mediumNot functioning - next quarter if capacity permitsseverity-mediumBug where workaround exists or that doesn't prevent the usage of Zowe. Just makes it more complex.

    Type

    No type

    Projects

    • Status

      Medium Priority

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions