-
Notifications
You must be signed in to change notification settings - Fork 93
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
ze(uss): Pulling from mainframe
status bar message does not get disposed of for binary files
#3355
Closed
Tracked by
#3166
Labels
bug
Something isn't working
severity-high
Bug for which there may be workaround but limits the usage of the Zowe for major use cases
Milestone
Comments
zFernand0
added
bug
Something isn't working
severity-low
Bug that makes the usage of the Zowe less convenient but doesn't impact key use cases
labels
Dec 11, 2024
Thank you for creating a bug report. |
15 tasks
15 tasks
Turns out that Pull from Mainframe never supported binary USS files. I'm going to address this in v2 as well. |
traeok
removed
good first issue
Good for newcomers
severity-low
Bug that makes the usage of the Zowe less convenient but doesn't impact key use cases
labels
Dec 12, 2024
traeok
added
the
severity-high
Bug for which there may be workaround but limits the usage of the Zowe for major use cases
label
Dec 12, 2024
github-project-automation
bot
moved this from In Progress
to Closed
in Zowe Explorer for VS Code
Dec 12, 2024
Keeping open until ported to v2 |
github-project-automation
bot
moved this from Closed
to New Issues
in Zowe Explorer for VS Code
Dec 12, 2024
15 tasks
github-project-automation
bot
moved this from In Progress
to Closed
in Zowe Explorer for VS Code
Dec 16, 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
severity-high
Bug for which there may be workaround but limits the usage of the Zowe for major use cases
Describe the bug
The status bar message doesn't go away when you open a USS file as binary and then pull from mainframe
To Reproduce
Pull from mainframe
Expected behavior
For the message to go away eventually 😋
Screenshots
Desktop (please complete the following information):
Additional context
Found while looking for a Download option for USS files and Dataset.
Thanks @roman-kupriyanov
Since the node's contextValue is
binaryFile
, theSharedContext.isDocument()
doesn't consider it as a valid document. Thus we remove it from the list.I think we just need to dispose of the status message outside the for-loop
The text was updated successfully, but these errors were encountered: