Bug #19681
closed
registered workflows in wb2 don't show default inputs
Description
You can see this the WGS registered workflow is playground
wb1:https://workbench.pirca.arvadosapi.com/container_requests/pirca-xvhdp-y5v4zana8tuif9k
wb2: I can't give you a page but if you go new -> run a workflow -> you can get a list of registered wfs - and choose the WGS one - and then there are no defaults.
Using the "Run" button in the side panel doesn't seem to fill in defaults.
However, when using the "New -> Process" menu, it fills in most of the defaults but not the "Directory of FASTQs" input parameter.
Updated by Peter Amstutz about 2 years ago
- Target version set to 2022-11-09 sprint
- Assigned To set to Peter Amstutz
- Category set to Workbench2
Updated by Peter Amstutz about 2 years ago
- Subject changed from registered workflows in wb2 don't how default inputs to registered workflows in wb2 don't show default inputs
Updated by Peter Amstutz about 2 years ago
- Target version changed from 2022-11-09 sprint to 2022-11-23 sprint
Updated by Peter Amstutz about 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 Peter Amstutz about 2 years ago
- Story points set to 2.0
- Assigned To deleted (
Peter Amstutz)
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 2022-12-21 Sprint
Updated by Peter Amstutz about 2 years ago
I don't think this is a bug. Or at least, not any more.
When I run pirca-j7d0g-chdv0xwrzxngtfn all of the inputs have default values. When I try to run it, all the default values are set as expected.
I found another one where the fastqdir input was not filled in, so we might have just gotten confused.
Playground's database is a mess.
Updated by Peter Amstutz almost 2 years ago
- Status changed from Closed to Feedback
Updated by Peter Amstutz almost 2 years ago
Ok, now I'm seeing this, it only seems to happen the 1st time, it's sort of hard to pin down.
Updated by Peter Amstutz almost 2 years ago
Ok fixed for real in arvados-workbench2|bdd9fd7a53ea02db15e23acb03f995ee42b0c594
Explicitly sets defaults in openRunProcess method.
Updated by Peter Amstutz almost 2 years ago
- Status changed from Feedback to Resolved