Feature #19295
closedShow container request "reused" status
Description
Workbench should indicate when a child workflow step was reused. This can be determined by checking if the container was created before the container request, e.g.
container.created_at < container_request.created_at
I think the best way to show this would be to display as a "Reused" status (in the same list as "Queued" "Running" "Complete" "Failed" etc).
However, since it's possible to share incomplete containers as well, it should only do this for containers that would otherwise show as "Complete". Containers which are in Queued/Running/Failed state should still show their state.
Updated by Peter Amstutz over 2 years ago
- Description updated (diff)
- Subject changed from Container request "reused" status to Show container request "reused" status
Updated by Peter Amstutz over 2 years ago
- Target version changed from 2022-08-17 sprint to 2022-08-31 sprint
Updated by Peter Amstutz over 2 years ago
- Target version changed from 2022-08-31 sprint to 2022-09-14 sprint
Updated by Peter Amstutz over 2 years ago
- Target version changed from 2022-09-14 sprint to 2022-09-28 sprint
Updated by Peter Amstutz over 2 years ago
- Target version changed from 2022-09-28 sprint to 2022-10-12 sprint
Updated by Peter Amstutz over 2 years ago
- Target version changed from 2022-10-12 sprint to 2022-10-26 sprint
Updated by Peter Amstutz over 2 years ago
- Target version changed from 2022-10-26 sprint to 2022-11-09 sprint
Updated by Peter Amstutz over 2 years ago
- Target version changed from 2022-11-09 sprint to 2022-11-23 sprint
Updated by Peter Amstutz over 2 years ago
- Target version changed from 2022-11-23 sprint to 2022-12-07 Sprint
Updated by Peter Amstutz about 2 years ago
- Target version changed from 2022-12-07 Sprint to 2022-12-21 Sprint
Updated by Stephen Smith about 2 years ago
- Story points changed from 1.0 to 2.0
Updated by Peter Amstutz about 2 years ago
- Target version changed from 2022-12-21 Sprint to 2023-01-18 sprint
Updated by Peter Amstutz about 2 years ago
- Target version changed from 2023-01-18 sprint to 2023-02-01 sprint
Updated by Peter Amstutz about 2 years ago
- Target version changed from 2023-02-01 sprint to 2023-02-15 sprint
Updated by Peter Amstutz about 2 years ago
- Target version changed from 2023-02-15 sprint to 2023-02-01 sprint
Updated by Peter Amstutz about 2 years ago
- Release set to 59
- Target version deleted (
2023-02-01 sprint)
Updated by Peter Amstutz about 2 years ago
- Target version set to To be scheduled
Updated by Peter Amstutz almost 2 years ago
- Story points changed from 2.0 to 1.0
- Target version changed from To be scheduled to Development 2023-04-12 sprint
- Assigned To set to Peter Amstutz
Updated by Peter Amstutz almost 2 years ago
19295-reused @ 756da23ade34fd225e80e448fb27795d453294c6
- Show "Reused" process state when
container.finished_at < container_request.created_at
I didn't compare on createdAt because the container can have a slightly earlier creation time when it is created in the same transaction as the container request. I chose to use finishedAt because most people will assume "reused" means no additional work needed to be done, so while it's possible to share a running container, calling it "reused" in that case is more likely to be confusing.
Updated by Lucas Di Pentima almost 2 years ago
Some comments:
- There're many compiler warnings that probably come from the previously merged branch that would be nice to fix.
- The update works OK but as it is, it creates a disconnect between all the available Status and the status filtering capabilities.
- It may be confusing to the user to request listing only Completed process and reading another label.
- They may even they want to only list the reused processes, to quickly assess how much work Arvados saves them.
Other than that, it LGTM.
Updated by Peter Amstutz almost 2 years ago
from review discussion, should also have a "cancelling" state when it is priority=0 but still running.
Updated by Peter Amstutz almost 2 years ago
The way the filter dropdown is set up, changing it to say "Completed and Reused" is actually sort of complicated, so I choose not to do it. We can revisit it if there is feedback about it.
We don't have a way purely with an API query to filter on reused/not reused processes.
I made a few other changes:
- Added "Cancelling" state for when the cancel button has been pushed (priority=0) but it is still running
- Tweaked the styling of the cancel button
- Tweaked the "Type" filter to reflect the relative ordering of workflow runs vs workflow definitions (the group contents API returns workflow definitions after workflow runs, unfortunately)
- Made intermediate and log collections hidden by default (this greatly reduces the clutter in the default view).
I verbally discussed these changes with the team, and since they are fairly low-risk changes I went ahead and merged this.
Updated by Peter Amstutz almost 2 years ago
- Status changed from New to Resolved
- Subject changed from Show container request "reused" status to Show container request "reused" status
Updated by Peter Amstutz almost 2 years ago
- Related to Idea #20287: Cancel button on WB2 should be filled in added
Updated by Peter Amstutz almost 2 years ago
- Related to Idea #20291: Add a re-used label for processes that are reused in WB2 added