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
The API query for getting all ORT runs for a repository is currently sortable by the index and created_at columns only. We have a UI view which also shows the Run Status and Duration for the runs:
Implementing client-side sorting for the table would be far too inefficient and lead to slow performance, so we would need the API endpoint to:
also be sortable by status field
calculate and return the duration of the run, and make that sortable. First implementation could be to just return the duration, be it for an ongoing or finished job, but that's debatable
Moreover, we use the same endpoint for this view:
For this table to be made sortable, we would need the endpoint to also
return total number of runs for the repository
last run status, and job statuses for it
timestamp of last run
be able to sort with: total number of runs, last run status, and timestamp of the last run
The text was updated successfully, but these errors were encountered:
Etsija
changed the title
The "Get all ORT runs for a repository" query needs more sorting options
The "Get all ORT runs for a repository" endpoint needs more sorting options
Feb 19, 2025
Etsija
changed the title
The "Get all ORT runs for a repository" endpoint needs more sorting options
The "Get all ORT runs for a repository" endpoint needs more data and sorting options
Feb 19, 2025
The API query for getting all ORT runs for a repository is currently sortable by the
index
andcreated_at
columns only. We have a UI view which also shows the Run Status and Duration for the runs:Implementing client-side sorting for the table would be far too inefficient and lead to slow performance, so we would need the API endpoint to:
status
fieldMoreover, we use the same endpoint for this view:
For this table to be made sortable, we would need the endpoint to also
The text was updated successfully, but these errors were encountered: