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

API /runs should return 404 instead of empty list #1461

Open
mfeit-internet2 opened this issue Aug 7, 2024 · 0 comments
Open

API /runs should return 404 instead of empty list #1461

mfeit-internet2 opened this issue Aug 7, 2024 · 0 comments
Assignees

Comments

@mfeit-internet2
Copy link
Member

mfeit-internet2 commented Aug 7, 2024

The /pscheduler/tasks/xxx/runs endpoint returns an empty list rather than the 404 it should if the task doesn't exist:

$ cpr https://ps01-l.farm.particle.cz/pscheduler/tasks/e24f7abc-21d2-4cb3-88dc-67d30cc38989/runs/74f58e57-178b-4112-9485-13dff578d041
Server returned 404:
Resource not found.
$ cpr https://ps01-l.farm.particle.cz/pscheduler/tasks/e24f7abc-21d2-4cb3-88dc-67d30cc38989/runs
[]
$ cpr https://ps01-l.farm.particle.cz/pscheduler/tasks/e24f7abc-21d2-4cb3-88dc-67d30cc38989
Server returned 404:
Resource not found.

Code is in `pscheduler-server/pscheduler-server/api-server/pschedulerapiserver/runs.py`
@github-project-automation github-project-automation bot moved this to Ready in perfSONAR Aug 7, 2024
@mfeit-internet2 mfeit-internet2 changed the title API /runs not returning 404 when it needs to API /runs not returning 404 when it needs to return an empty list Sep 18, 2024
@mfeit-internet2 mfeit-internet2 changed the title API /runs not returning 404 when it needs to return an empty list API /runs should return 404 instead of empty list Dec 2, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: Ready
Development

When branches are created from issues, their pull requests are automatically linked.

2 participants