USS files menu serves incorrect content from another directory

[ChrisBoehmCA]

Describe the bug

To Reproduce

I am not sure exactly what causes this, but I think is the fact that I have been viewing two directories with similar structure. What happens is that once you change filters, similarly named files from a previous filter are downloaded instead of those for the active filter. It's hard to show an example since the path names are sensitive info, but here's a visual:

So connect to a profile and click the USS section. Try setting up these USS files.

/u/users/abc/hello/hello.log

and

/u/users/def/hello/hello.log

Try setting a filter for /u/users/def first and downloading hello/hello.log.

Then try to change your filter to /u/users/abc and try to download hello/hello.log. If this reproduction was sufficient you will see that it downloads to the /u/users/def path instead of a new path. I would guess this is caused by using the relative path as the unique identifier for a file, but the absolute path must be used instead. Either way, changing the directory or deleting the old file manually does not fix the issue. I guess restarting VS Code would be the only solution right now.

Expected behavior

The file is served from the currently selected directory instead of a previously selected one.

Screenshots

Desktop (please complete the following information):

• OS: Windows 10
• Zowe Explorer Version: v1.11.1
• (Optional) Zowe CLI Version: 6.24.2
• (Optional) Are you using Secure Credential Store? No

Additional context

[zdmullen]

This could be related in part to #650 . @lauren-li will look into it.

[ChrisBoehmCA]

I can't use Zowe Explorer unless this is fixed as the wrong files are uploaded and downloaded when I edit. Seems like the related issue changed priority a few times.

[lauren-li]

I was debugging this, and it seems like the absolute path is actually being used; however, it is not getting updated everywhere it needs to be when running a new search. I am looking into why this is the case.

The related issue (#650) is also being worked on (and upon further investigation, does not actually seem very related). It has been moved around a bit as the Zowe Explorer squad was arranging issues in a new project board after PI planning. Apologies for the confusion there, but I am trying to get it in for the next Zowe Explorer release (1.13.0).

[ChrisBoehmCA]

Okay thank you. I appreciate it

…

On Tue, Mar 2, 2021 at 7:24 AM Lauren Li ***@***.***> wrote: I was debugging this, and it seems like the absolute path is actually being used; however, it is not getting updated everywhere it needs to be when running a new search. I am looking into why this is the case. The related issue (#650 <#650>) is also being worked on (and upon further investigation, does not actually seem very related). It has been moved around a bit as the Zowe Explorer squad was arranging issues in a new project board after PI planning. Apologies for the confusion there, but I am trying to get it in for the next Zowe Explorer release (1.13.0). — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#1134 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AKETESMH6I3GFKC6BA3OTZDTBTKJNANCNFSM4V6CG54A> .

-- This electronic communication and the information and any files transmitted with it, or attached to it, are confidential and are intended solely for the use of the individual or entity to whom it is addressed and may contain information that is confidential, legally privileged, protected by privacy laws, or otherwise restricted from disclosure to anyone else. If you are not the intended recipient or the person responsible for delivering the e-mail to the intended recipient, you are hereby notified that any use, copying, distributing, dissemination, forwarding, printing, or copying of this e-mail is strictly prohibited. If you received this e-mail in error, please return the e-mail to the sender, delete it from your computer, and destroy any printed copy of it.

[lauren-li]

@ChrisBoehmCA This issue is being addressed by PR #1229 (Bugfix issue 1134: Add parentPath check for existing USS node children). The PR description has more details on what the root issue was and how it was fixed. Please feel free to check it out and give it a try!

[ChrisBoehmCA]

Thanks for the update. If I get a chance I will try to build from source from that branch and try it out