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

Sort the experiments by last run time #249

Closed
Ark-kun opened this issue Nov 14, 2018 · 6 comments
Closed

Sort the experiments by last run time #249

Ark-kun opened this issue Nov 14, 2018 · 6 comments
Assignees
Labels
area/api area/backend area/frontend help wanted The community is welcome to contribute. kind/feature lifecycle/stale The issue / pull request is stale, any activities remove this label. needs investigation priority/p2

Comments

@Ark-kun
Copy link
Contributor

Ark-kun commented Nov 14, 2018

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.

@yebrahim
Copy link
Contributor

yebrahim commented Nov 14, 2018

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.
/cc @IronPan.

@vicaire
Copy link
Contributor

vicaire commented Mar 27, 2019

Assigning to @ajayalfred to comment on whether this is something we would like to have from the UX perspective.

@ajayalfred
Copy link
Contributor

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.

@Bobgy
Copy link
Contributor

Bobgy commented Jan 22, 2020

@jingzhang36 Do you think this is possible with our current backend?

@Bobgy Bobgy added help wanted The community is welcome to contribute. needs investigation labels Jan 22, 2020
@stale
Copy link

stale bot commented Jun 24, 2020

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.

@stale stale bot added the lifecycle/stale The issue / pull request is stale, any activities remove this label. label Jun 24, 2020
@stale
Copy link

stale bot commented Jul 1, 2020

This issue has been automatically closed because it has not had recent activity. Please comment "/reopen" to reopen it.

@stale stale bot closed this as completed Jul 1, 2020
Linchin pushed a commit to Linchin/pipelines that referenced this issue Apr 11, 2023
…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.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/api area/backend area/frontend help wanted The community is welcome to contribute. kind/feature lifecycle/stale The issue / pull request is stale, any activities remove this label. needs investigation priority/p2
Projects
None yet
Development

No branches or pull requests

10 participants