Closed evan-wehi closed 7 years ago
It's not the best solution, but you may try to run it with --non-strict flag. It will allow to ignore these warnings
Hello @evan-wehi
Thank you for reporting your issue. This is a regression in cwltool
-- I thought we had documented it already, but evidently not. I'm moving the issue to https://github.com/common-workflow-language/cwltool/issues/455
Thanks for looking at it @mr-c
Evan.
From: Michael R. Crusoe [mailto:notifications@github.com] Sent: 06 July 2017 20:57 To: common-workflow-language/workflows workflows@noreply.github.com Cc: Evan Thomas thomas.e@wehi.edu.au; Mention mention@noreply.github.com Subject: Re: [common-workflow-language/workflows] Did you include a $schemas section? (#137)
Hello @evan-wehihttps://github.com/evan-wehi
Thank you for reporting your issue. This is a regression in cwltool -- I thought we had documented it already, but evidently not. I'm moving the issue to common-workflow-language/cwltool#455https://github.com/common-workflow-language/cwltool/issues/455
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHubhttps://github.com/common-workflow-language/workflows/issues/137#issuecomment-313364370, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AVADDe4DbsHHQjYwgvuqvUy-iARJVFDPks5sLL2BgaJpZM4OPKHk.
Hello,
I'm building a workflow and using CommandLineTool examples from this repository (which are great!). Many have metadata but including them in a workflow produces:
This example uses the
samtools-sort.cwl
directly from the repository (other than commenting out the imports forenvvar-global.ylm
andsamtools-docker.yml
)