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

The "Get all ORT runs for a repository" endpoint needs more data and sorting options #2047

Open
Etsija opened this issue Feb 19, 2025 · 0 comments
Labels
api Issues related to the API.

Comments

@Etsija
Copy link
Contributor

Etsija commented Feb 19, 2025

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:

Image

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:

Image

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
@Etsija Etsija added api Issues related to the API. enhancement labels Feb 19, 2025
@Etsija 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 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
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
api Issues related to the API.
Projects
None yet
Development

No branches or pull requests

2 participants