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

[z/OSMF profiles] Data Set and USS list API calls do not pass responseTimeout #3225

Closed
Tracked by #3250
traeok opened this issue Oct 10, 2024 · 1 comment · Fixed by #3292
Closed
Tracked by #3250

[z/OSMF profiles] Data Set and USS list API calls do not pass responseTimeout #3225

traeok opened this issue Oct 10, 2024 · 1 comment · Fixed by #3292
Assignees
Labels
bug Something isn't working needs-ported Apply to issues or PRs that need ported priority-high Production outage - this quarter or at least next quarter severity-high Bug for which there may be workaround but limits the usage of the Zowe for major use cases v3
Milestone

Comments

@traeok
Copy link
Member

traeok commented Oct 10, 2024

Describe the bug

When we list data sets or USS files in Zowe Explorer, we do not pass the responseTimeout property from the profile to these SDK calls.

To Reproduce

  • Execute a data set search query for a pattern that matches several data sets (>250, for example)
  • Notice that the request never comes back as the default timeout is exceeded, and the timeout specified on the profile is not respected.

Expected behavior

The list operation for data sets and USS files should respect the responseTimeout property defined on a z/OSMF profile.

Screenshots

Desktop (please complete the following information):

  • OS: Windows 10
  • Zowe Explorer Version: 3.0.0
  • (Optional) Zowe CLI Version:
  • (Optional) Are you using Secure Credential Store?
@traeok traeok added the bug Something isn't working label Oct 10, 2024
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.

@traeok traeok added v2 v3 needs-ported Apply to issues or PRs that need ported and removed v2 labels Oct 10, 2024
@JillieBeanSim JillieBeanSim added this to the v3.1.0 milestone Oct 14, 2024
@zFernand0 zFernand0 added priority-high Production outage - this quarter or at least next quarter severity-high Bug for which there may be workaround but limits the usage of the Zowe for major use cases labels Oct 17, 2024
@traeok traeok self-assigned this Oct 17, 2024
@zowe-robot zowe-robot moved this from New Issues to High Priority in Zowe Explorer for VS Code Oct 17, 2024
@traeok traeok linked a pull request Nov 4, 2024 that will close this issue
15 tasks
@github-project-automation github-project-automation bot moved this from High Priority to Closed in Zowe Explorer for VS Code Nov 5, 2024
@JillieBeanSim JillieBeanSim modified the milestones: v3.1.0, v3.0.3 Nov 6, 2024
@zFernand0 zFernand0 mentioned this issue Nov 14, 2024
15 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working needs-ported Apply to issues or PRs that need ported priority-high Production outage - this quarter or at least next quarter severity-high Bug for which there may be workaround but limits the usage of the Zowe for major use cases v3
Projects
Status: Closed
Development

Successfully merging a pull request may close this issue.

3 participants