-
-
Notifications
You must be signed in to change notification settings - Fork 231
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
cwltool --print-deps fails with workflows having namespaced location steps #1765
Comments
Huh, that error message is really odd since the
|
Oh wow, I never thought about using namespace for file references that way. That is really clever. I believe what is happening is that the |
Ah! In that case I think we can just switch the order, and load and validate the document before Thanks @tetron ! |
I have been testing to "print" the list of dependencies of several workflows which have some of its steps declarations outside their workflow repository. I need them to be able to capture the list of all the CWL URLs involved in a workflow.
Expected Behavior
For instance, if you test next workflow:
git clone https://github.com/Sage-Bionetworks-Challenges/data-to-model-challenge-workflow cd data-to-model-challenge-workflow cwltool --print-deps --relative-deps primary workflow.cwl
it provides the list of both local and remote cwl dependencies.
Actual Behavior
But, with workflows where the base location is declared as a namespace, and then the namespace is used to declare the step location in a shorter way, next operation is failing:
git clone https://github.com/pvanheus/lukasa/ cd lukasa cwltool --print-deps --relative-deps primary protein_evidence_mapping.cwl
Workflow Code
You can see one example of workflow using namespaces to provide the "prefix" to locate the steps in next link https://github.com/pvanheus/lukasa/blob/main/protein_evidence_mapping.cwl . There are more examples available in other GitHub repos.
Full Traceback
Your Environment
All the tests have been with cwltool 3.1.20221109155812 in Linux.
The text was updated successfully, but these errors were encountered: