-
Notifications
You must be signed in to change notification settings - Fork 295
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
Some methods return 2xx codes instead of 404 when the task does not exist. #38
Comments
vgopari
pushed a commit
to vgopari/conductor
that referenced
this issue
Feb 11, 2024
…ds handling non-existent tasks
vgopari
pushed a commit
to vgopari/conductor
that referenced
this issue
Feb 11, 2024
…ds handling non-existent tasks
vgopari
pushed a commit
to vgopari/conductor
that referenced
this issue
Feb 11, 2024
…ds handling non-existent tasks
vgopari
pushed a commit
to vgopari/conductor
that referenced
this issue
Feb 15, 2024
vgopari
pushed a commit
to vgopari/conductor
that referenced
this issue
Mar 4, 2024
…points handling non-existent tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug
Some methods return 2xx codes instead of 404 when the task does not exist.
For example
POST /api/tasks/{task_id}/log -> Return 200 when task does not exists
GET /api/tasks/{task_id} -> Return 204 when task does not exists
Details
Conductor version: v3.14.0
Persistence implementation: MySQL
Expected behavior
When a request is made to a resource (e.g. a task) if it does not exist return code 404.
The text was updated successfully, but these errors were encountered: