-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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
Sort the experiments by last run time #249
Comments
Seems like there's quite a few asks here. To address the concern in the issue title though, this should be an API request, and I don't think the current design of the backend allows for sorting on mutable columns, let alone computed columns like this. |
Assigning to @ajayalfred to comment on whether this is something we would like to have from the UX perspective. |
Yes, we want the latest runs to appear at the top of the list. In general, all tables should be default sorted by timestamp with the most recent resource appearing at the top of the list. |
@jingzhang36 Do you think this is possible with our current backend? |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
This issue has been automatically closed because it has not had recent activity. Please comment "/reopen" to reopen it. |
…low#300) * Create a cron job to regularly garbage collect test resources. * Add to cleanup_ci.py an "all" subcommand to delete all resources." * Add a batch job for one off runs. Related to: kubeflow#87 Cron job to garbage collect test resources kubeflow#249 cron job to collect Kubeflow deployments launched by E2E tests * * Add a cron job to run the cleanup every two hours. * In cleanup_ci.py; don't load the imports of the manifests We encountered an error where the manifest didn't exist. I think that may have been a collision because we had a separate script running to do the deletes. * Fix some bugs. * Deal with config being none. * Maybe activate service account.
Multiple times I have made a mistake and created experiment when all I wanted was to create a run. ( #53 )
Now I have more than 10 experiments (did someone test this?) and all my runs are in the first experiment which is shown last.
Every time I need to see my new run, I need to first locate the experiment (due to #64 #58 #57)
To locate the experiment I have to go to the next page every time (because the UI does not remember the last page I was on #62).
It would be great if the experiment list was sorted by the latest run time (this issue). Having #64 fixed would make it even better.
The text was updated successfully, but these errors were encountered: