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

Regression on: fix(ProfilesCache): Clear object caches before refresh #2795 #2910

Closed
FrankSu1996 opened this issue May 10, 2024 · 3 comments · Fixed by #2917
Closed

Regression on: fix(ProfilesCache): Clear object caches before refresh #2795 #2910

FrankSu1996 opened this issue May 10, 2024 · 3 comments · Fixed by #2917
Assignees
Labels
bug Something isn't working priority-medium Not functioning - next quarter if capacity permits severity-medium Bug where workaround exists or that doesn't prevent the usage of Zowe. Just makes it more complex.
Milestone

Comments

@FrankSu1996
Copy link

FrankSu1996 commented May 10, 2024

Describe the bug

Issue #2795 seems to have regressed. When the fix came out in v2.15.2, I tested it and it worked. Today, I stumbled across the behavior again, where removing the single instance of our profile type still caused the ProfilesCache to hold onto the stale reference. The only other thing that has changed in my VsCode environment that I could think of is the zowe-explorer version and VsCode version.

To Reproduce

Steps to reproduce the behavior:

  1. Contribute new profile type using zowe-explorer-api.
  2. Create a team config file. Doesn't matter if it's global/project
  3. Delete the single instance of the contributed profile, and call ProfilesCache.refresh()

Expected behavior

ProfilesCache should correctly remove the profile. But it doesn't.

Screenshots

Desktop (please complete the following information):

  • OS: Windows 11
  • zowe-explorer-api version: 2.15.2, also tried with latest 2.15.3
  • zowe-explorer version: 2.15.4
  • VsCode version: 1.89.1
  • (Optional) Zowe CLI Version:
  • (Optional) Are you using Secure Credential Store? yes
Copy link

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.

@t1m0thyj
Copy link
Member

This may be related to #2888

@t1m0thyj t1m0thyj self-assigned this May 14, 2024
@t1m0thyj t1m0thyj linked a pull request May 15, 2024 that will close this issue
16 tasks
@t1m0thyj t1m0thyj added priority-medium Not functioning - next quarter if capacity permits severity-medium Bug where workaround exists or that doesn't prevent the usage of Zowe. Just makes it more complex. labels May 15, 2024
@zowe-robot zowe-robot moved this from New Issues to Medium Priority in Zowe Explorer for VS Code May 15, 2024
@JillieBeanSim JillieBeanSim modified the milestones: v2.16.0, v2.16.1 May 16, 2024
@JillieBeanSim
Copy link
Contributor

JillieBeanSim commented May 21, 2024

closing with merge of attached PR

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-medium Not functioning - next quarter if capacity permits severity-medium Bug where workaround exists or that doesn't prevent the usage of Zowe. Just makes it more complex.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants