-
Notifications
You must be signed in to change notification settings - Fork 6
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
CWL workflow outputs within nested binding not handled #371
Comments
@lhcorralo Note that your step |
…kflow collect output glob (fix #371)
Thank you for noticing the missing "blur" parameter :) I just wanted to confirm that if I do not use nested folders, version 4.4 is running fine 👍 Let me know if I can help in any way |
…kflow collect output glob (fix #371)
@lhcorralo |
…kflow collect output glob (fix #371)
…kflow collect output glob (fix #371)
As presented in: #358 (comment)
Workflows that define nested directories such as
outputBindings: {glob: "somedir/*.patterm"}
do not find outputs for mapping fromstep(i) out ->step(i+1) in
because thesomedir
hierarchy is not preserved since results are staged-in for remote directly under job UUID.Sample definitions to test:
Again, the workflow is failing with the following error:
Originally posted by @lhcorralo in #358 (comment)
The text was updated successfully, but these errors were encountered: