cwltool conflict version?
See original GitHub issueHi,
I’m trying to run a CWL workflow for bcbio-nextgen in our SLURM cluster using Toil. To do so, I’m running the following command: cwltoil --verbose --preserve-environment PATH HOME --no-container run_info-cwl-workflow/main-run_info-cwl.cwl run_info-cwl-workflow/main-run_info-cwl-samples.json
.
The command is the same than the one specified in bcbio-nextgen docs, just that I use cwltoil
instead of cwltool
.
When doing so, I’m getting the following error:
login01 /scratch/gcarrasco/tests/test_bcbio_cwl ~> cwltoil --verbose --preserve-environment PATH HOME --no-container run_info-cwl-workflow/main-run_info-cwl.cwl run_info-cwl-workflow/main-run_info-cwl-samples.json Traceback (most recent call last):
File "/cm/shared/apps/bcbio/20150720-devel/data/anaconda/bin/cwltoil", line 9, in <module>
load_entry_point('toil==3.2.0a2', 'console_scripts', 'cwltoil')()
File "/cm/shared/apps/bcbio/20150720-devel/data/anaconda/lib/python2.7/site-packages/setuptools-20.2.2-py2.7.egg/pkg_resources/__init__.py", line 549, in load_entry_point
File "/cm/shared/apps/bcbio/20150720-devel/data/anaconda/lib/python2.7/site-packages/setuptools-20.2.2-py2.7.egg/pkg_resources/__init__.py", line 2542, in load_entry_point
File "/cm/shared/apps/bcbio/20150720-devel/data/anaconda/lib/python2.7/site-packages/setuptools-20.2.2-py2.7.egg/pkg_resources/__init__.py", line 2201, in load
File "/cm/shared/apps/bcbio/20150720-devel/data/anaconda/lib/python2.7/site-packages/setuptools-20.2.2-py2.7.egg/pkg_resources/__init__.py", line 2218, in require
File "/cm/shared/apps/bcbio/20150720-devel/data/anaconda/lib/python2.7/site-packages/setuptools-20.2.2-py2.7.egg/pkg_resources/__init__.py", line 835, in resolve
pkg_resources.VersionConflict: (cwltool 1.0.20160422204730 (/cm/shared/apps/bcbio/20150720-devel/data/anaconda/lib/python2.7/site-packages/cwltool-1.0.20160422204730-py2.7.egg), Requirement.parse('cwltool==1.0.20160413143011'))
Looking at the code I saw that the version of cwltool
required is set in setup.py
. Isn’t this a too strict requirement? I’d suggest changing it for
'cwl': [
'cwltool>=1.0]},
Ping @tetron 😃
Issue Analytics
- State:
- Created 7 years ago
- Comments:5 (5 by maintainers)
Top Results From Across the Web
cwltool and pyparsing version conflict in v22.01 - Galaxy Help
Hi, All. When attempting to update to v22.01 using ansible, we seem to be running into a version conflict between the versions of...
Read more >conflict-wf.cwl#collision - Common Workflow Language Viewer
- Download as Research Object Bundle [?]. Verified with cwltool version 1.0.20180525185854. Permalink: [?] https://w3id.org/cwl/view/git ...
Read more >common-workflow-language/cwltool: 3.0.20201203173111
When collecting output, now correctly looks for loadListing in outputBinding Fix a long standing issue where empty, unused, randomly named ...
Read more >Common Workflow Language reference implementation
If there is a conflict between a third party package dependency which has dropped support for a Python version that cwltool should support ......
Read more >Conda and BioConda · BioExcel Best Practice Guide
As bioconda/toil depend on a particular version of cwltool , install that first. If you desire a newer cwltool create a separate Conda...
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
So yes, https://github.com/BD2KGenomics/toil/blob/master/setup.py#L43 should be changed to use a
>=
a known working version.Use of ‘>=’ version constraints are discouraged. See #827 for discussion.