Dockstore CLI Fails Launching a WDL with Imports
See original GitHub issueBug Report
The following checker workflow has WDL imports. You get an NPE when you try to launch it:
dockstore workflow launch --entry github.com/DataBiosphere/topmed-workflows/u_of_Michigan_alignment_pipeline_wdl_checker:1.29.0 --json foo.json
15:15:23.562 [main] ERROR io.dockstore.client.cli.ArgumentUtility - Could not get WDL imports: null
15:15:23.567 [main] ERROR io.dockstore.client.cli.ArgumentUtility - java.lang.NullPointerException
at wdl4s.wdl.WdlNamespace$.apply(WdlNamespace.scala:216)
at wdl4s.wdl.WdlNamespace$$anonfun$wdl4s$wdl$WdlNamespace$$load$1.apply(WdlNamespace.scala:179)
at wdl4s.wdl.WdlNamespace$$anonfun$wdl4s$wdl$WdlNamespace$$load$1.apply(WdlNamespace.scala:179)
at scala.util.Try$.apply(Try.scala:192)
at wdl4s.wdl.WdlNamespace$.wdl4s$wdl$WdlNamespace$$load(WdlNamespace.scala:178)
at wdl4s.wdl.WdlNamespace$$anonfun$20.apply(WdlNamespace.scala:209)
at wdl4s.wdl.WdlNamespace$$anonfun$20.apply(WdlNamespace.scala:207)
at scala.collection.TraversableLike$$anonfun$map$1.apply(TraversableLike.scala:234)
at scala.collection.TraversableLike$$anonfun$map$1.apply(TraversableLike.scala:234)
at scala.collection.immutable.List.foreach(List.scala:392)
at scala.collection.TraversableLike$class.map(TraversableLike.scala:234)
at scala.collection.immutable.List.map(List.scala:296)
at wdl4s.wdl.WdlNamespace$.apply(WdlNamespace.scala:207)
at wdl4s.wdl.WdlNamespace$$anonfun$wdl4s$wdl$WdlNamespace$$load$1.apply(WdlNamespace.scala:179)
at wdl4s.wdl.WdlNamespace$$anonfun$wdl4s$wdl$WdlNamespace$$load$1.apply(WdlNamespace.scala:179)
at scala.util.Try$.apply(Try.scala:192)
at wdl4s.wdl.WdlNamespace$.wdl4s$wdl$WdlNamespace$$load(WdlNamespace.scala:178)
at wdl4s.wdl.WdlNamespace$.loadUsingSource(WdlNamespace.scala:175)
at wdl4s.wdl.WdlNamespaceWithWorkflow$.load(WdlNamespace.scala:555)
at io.dockstore.common.Bridge.getInputFiles(Bridge.scala:91)
at io.github.collaboratory.wdl.WDLClient.launch(WDLClient.java:151)
at io.dockstore.client.cli.nested.WorkflowClient.launch(WorkflowClient.java:436)
at io.dockstore.client.cli.nested.AbstractEntryClient.processEntryCommands(AbstractEntryClient.java:226)
at io.dockstore.client.cli.Client.run(Client.java:706)
at io.dockstore.client.cli.Client.main(Client.java:608)```
Here is the foo.json, used as an input:
"checkerWorkflow.input_cram_file": "https://storage.googleapis.com/topmed_workflow_testing/topmed_aligner/input_files/NWD176325.25reads.cram",
"checkerWorkflow.input_crai_file": "https://storage.googleapis.com/topmed_workflow_testing/topmed_aligner/input_files/NWD176325.25reads.cram.crai",
"checkerWorkflow.inputTruthCRAMFile": "https://storage.googleapis.com/topmed_workflow_testing/topmed_aligner_checker/truth_NWD176325.25reads.cram",
"checkerWorkflow.ref_alt": "https://storage.googleapis.com/topmed_workflow_testing/topmed_aligner/reference_files/hg38/hs38DH.fa.alt",
"checkerWorkflow.ref_bwt": "https://storage.googleapis.com/topmed_workflow_testing/topmed_aligner/reference_files/hg38/hs38DH.fa.bwt",
"checkerWorkflow.ref_pac": "https://storage.googleapis.com/topmed_workflow_testing/topmed_aligner/reference_files/hg38/hs38DH.fa.pac",
"checkerWorkflow.ref_ann": "https://storage.googleapis.com/topmed_workflow_testing/topmed_aligner/reference_files/hg38/hs38DH.fa.ann",
"checkerWorkflow.ref_amb": "https://storage.googleapis.com/topmed_workflow_testing/topmed_aligner/reference_files/hg38/hs38DH.fa.amb",
"checkerWorkflow.ref_sa": "https://storage.googleapis.com/topmed_workflow_testing/topmed_aligner/reference_files/hg38/hs38DH.fa.sa",
"checkerWorkflow.ref_fasta": "https://storage.googleapis.com/topmed_workflow_testing/topmed_aligner/reference_files/hg38/hs38DH.fa",
"checkerWorkflow.ref_fasta_index": "https://storage.googleapis.com/topmed_workflow_testing/topmed_aligner/reference_files/hg38/hs38DH.fa.fai",
"checkerWorkflow.dbSNP_vcf": "https://storage.googleapis.com/topmed_workflow_testing/topmed_aligner/reference_files/hg38/Homo_sapiens_assembly38.dbsnp138.vcf.gz",
"checkerWorkflow.dbSNP_vcf_index": "https://storage.googleapis.com/topmed_workflow_testing/topmed_aligner/reference_files/hg38/Homo_sapiens_assembly38.dbsnp138.vcf.gz.tbi",
"checkerWorkflow.docker_image": "statgen/alignment:1.0.0"
}```
┆Issue is synchronized with this [Jira Bug](https://ucsc-cgl.atlassian.net/browse/DOCK-95)
┆Issue Number: DOCK-95
┆Sprint: Backlog
┆Issue Type: Bug
Issue Analytics
- State:
- Created 5 years ago
- Comments:13 (13 by maintainers)
Top Results From Across the Web
Dockstore CLI Fails Launching a WDL with Imports #1847
Bug Report The following checker workflow has WDL imports. You get an NPE when you try to launch it: dockstore workflow launch --entry ......
Read more >The `dockstore tool launch` wrongly complains missing ...
The dockstore tool launch complains with the following error message in the case of using “sub-workflow” in another WDL file.
Read more >Advanced CLI Features
By default, the Dockstore CLI launches CWL tools/workflows using cwltool. ... Cromwell requires imports of a workflow to be given in a zip...
Read more >Dockstore CLI FAQ
I was running a WDL locally, but some of my tasks are failing randomly and/or now I cannot use Docker. The CLI is...
Read more >WDL Training — Dockstore documentation
The Dockstore CLI can be used to run WDL workflows, among other things. Here we will use it to run a Hello World...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Verified this with staging, using Cromwell 36.
My ~/.dockstore/config settings:
And I did an
EXPORT DOCKSTORE_VERSION=1.5.3
The workflow failed at the very end, running on a Mac, due to a known problem with the workflow that Walt is going to look into, but it is unrelated to the provisioning that this bug fixes. Here’s the output when running the Java program:
cc: @wshands
I think this workflow doesn’t work with Cromwell 30.2. I think I ran it successfully with Cromwell 36. Will try later today. Sorry for the confusion.