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

AWS Batch API - ListJobs response missing 'statusReason' when request params include 'filters' #4587

Closed
andyluong1998 opened this issue Feb 21, 2024 · 2 comments
Assignees
Labels
bug This issue is a bug. closed-for-staleness p2 This is a standard priority issue response-requested Waiting on additional info and feedback. Will move to \"closing-soon\" in 7 days.

Comments

@andyluong1998
Copy link

Describe the bug

Expected Behavior

...

Current Behavior

...

Reproduction Steps

  • Request the API with filters

Possible Solution

No response

Additional Information/Context

No response

SDK version used

2, 3

Environment details (OS name and version, etc.)

AWS Linux 2023

@andyluong1998 andyluong1998 added bug This issue is a bug. needs-triage This issue or PR still needs to be triaged. labels Feb 21, 2024
@RanVaknin RanVaknin self-assigned this Mar 8, 2024
@RanVaknin
Copy link
Contributor

Hi @andyluong1998 ,

In order for us to further investigate this, can you please provide the following:

  1. A complete code snippet of your code needed to reproduce this.
  2. try running the same command using the CLI and see if the response returned there is the same or different.

Question: Could you be filtering out jobs that have the statusReason and the filtered results do not have statusReason on them?

Thanks,
Ran~

@RanVaknin RanVaknin added response-requested Waiting on additional info and feedback. Will move to \"closing-soon\" in 7 days. p2 This is a standard priority issue and removed needs-triage This issue or PR still needs to be triaged. labels Mar 8, 2024
Copy link

This issue has not received a response in 1 week. If you still think there is a problem, please leave a comment to avoid the issue from automatically closing.

@github-actions github-actions bot added closing-soon This issue will automatically close in 4 days unless further comments are made. closed-for-staleness and removed closing-soon This issue will automatically close in 4 days unless further comments are made. labels Mar 19, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug This issue is a bug. closed-for-staleness p2 This is a standard priority issue response-requested Waiting on additional info and feedback. Will move to \"closing-soon\" in 7 days.
Projects
None yet
Development

No branches or pull requests

2 participants