You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
Making a GET request to the /tasks endpoint proTES with an empty body always returns an empty list of tasks, even when a task has been created. This is because of this line in task_runs.py. Without a name prefix, str(kwargs.get("name_prefix")) returns the string "None" meaning name_prefix is not None is always True. As a result, a filter of "^None" is applied when querying the db.
To Reproduce
Steps to reproduce the behavior:
Run proTES
Create a task (POST to /tasks with valid body (e.g. {"executors": [{"image": "alpine", "command": ["echo", "hello"]}]})
Get list of tasks (GET to /tasks with empty body)
Task list is empty
Expected behavior
The task list should contain the newly created task ID and status.
Screenshots
POST request made successfully:
GET request returns empty task list:
The text was updated successfully, but these errors were encountered:
Describe the bug
Making a GET request to the
/tasks
endpoint proTES with an empty body always returns an empty list of tasks, even when a task has been created. This is because of this line intask_runs.py
. Without a name prefix,str(kwargs.get("name_prefix"))
returns the string"None"
meaningname_prefix is not None
is always True. As a result, a filter of"^None"
is applied when querying the db.To Reproduce
Steps to reproduce the behavior:
{"executors": [{"image": "alpine", "command": ["echo", "hello"]}]}
)Expected behavior
The task list should contain the newly created task ID and status.
Screenshots

POST request made successfully:
GET request returns empty task list:

The text was updated successfully, but these errors were encountered: