Actions
Bug #20493
closedOptional file array inputs are not rendered even when defined
Status:
Resolved
Priority:
Normal
Assigned To:
Category:
Workbench2
Target version:
Story points:
-
Release:
Release relationship:
Auto
Description
Reported that:
- In the process I/O panel, an input file array was displayed as "can't show" instead of rendering as expected
- In the panel to launch a workflow, allegedly the file array input isn't usable
Need to reproduce this, add a test, and fix it if there's an issue.
The parameter "fastqfile" shows "Cannot display value".
Here's the input type:
inputs: [ { "default": null, "id": "#main/fastqfile", "type": [ "null", { "items": "File", "type": "array" } ] } ]
Here's the input value:
{ "fastqfile": [ { "basename": "A427.fastq.gz", "class": "File", "http://arvados.org/cwl#collectionUUID": "zzzzz-...", "location": "keep:.../A427.fastq.gz", "size": 12345 } ] }
The type being "null" or "file array" means it is an optional input. Do the I/O panels handle optional inputs?
Files
Updated by Peter Amstutz over 1 year ago
- Target version changed from Development 2023-05-10 sprint to Development 2023-05-24 sprint
Updated by Peter Amstutz over 1 year ago
- Assigned To changed from Peter Amstutz to Brett Smith
Brett will try to reproduce
Updated by Peter Amstutz over 1 year ago
Peter will look at it on customer cluster
Updated by Peter Amstutz over 1 year ago
- Assigned To changed from Brett Smith to Stephen Smith
Updated by Brett Smith over 1 year ago
- Subject changed from File array inputs not working to Optional file array inputs are not rendered even when defined
- File cat.cwl cat.cwl added
Do the I/O panels handle optional inputs?
Confirmed they do not. If you register the attached workflow, in_files
is listed in Workbench 2 as "Cannot display value." Here it is on pirca.
Updated by Peter Amstutz over 1 year ago
20493-optional-array @ e11a6fa13214f91ffc602e53574736174ca6e8e9
Updated by Peter Amstutz over 1 year ago
- Assigned To changed from Stephen Smith to Peter Amstutz
Updated by Peter Amstutz over 1 year ago
- Status changed from New to In Progress
Updated by Peter Amstutz over 1 year ago
- Status changed from In Progress to Resolved
Actions