CWL workflows cannot read from S3
See original GitHub issueAs noted by @boyangzhao in https://github.com/DataBiosphere/toil/issues/4091#issuecomment-1122732414, toil-cwl-runner
does not seem to be able to read a CWL File
object with a location
set to an S3 URL:
txt_file:
class: File
location: s3://test/test.cwl
We should fix this, and add a test so this can’t break again.
This might be a problem for the upcoming AGC release.
┆Issue is synchronized with this Jira Story ┆friendlyId: TOIL-1165
Issue Analytics
- State:
- Created a year ago
- Comments:13 (9 by maintainers)
Top Results From Across the Web
Single CWL tools run without a workflow cannot read from S3 when ...
If I do: cat >helloworld.cwl <<'EOF' class: CommandLineTool cwlVersion: v1.0 id: ... Single CWL tools run without a workflow cannot read from S3...
Read more >Quickstart Examples — Toil 3.10.1 documentation
Running CWL workflows using Toil is easy. First ensure that Toil is installed with the cwl extra (see Installing extra features).
Read more >Trouble Shooting - Genomics Workflows on AWS
A file required by the workflow cannot be found at the specified S3 Path. Your workflow inputs might have the incorrect path OR...
Read more >Five things to consider when moving your research workflows ...
To compute using data on Amazon S3, copy it to the file system on Amazon ... See the Common Workflow Language (CWL) and...
Read more >Getting Started with CWL - Dockstore Documentation!
Dockstore does not support sbg:draft-2 CWL tools and workflows, ... should label your CWL with the version you are using so that CWL...
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
thanks! It looks like it fixed now, and confirm it’s working on my test examples.
OK, I’ve managed to reproduce the problem you are seeing. It seems to only happen when you run a single
CommandLineTool
as your main CWL document, and wrapping it in aWorkflow
makes the problem go away.I’ve opened #4125 to track this.