Open matthewfeickert opened 5 months ago
Hi @matthewfeickert ,
I can reproduce the issue locally, I will keep you updated!
PS: reana-client download
defaults to downloading all the output
files and directories specified in reana.yaml
. It seems like the examples/rome
workflow does not specify any outputs , so reana-client download
would not download any files anyway even if it worked without issues. In any case, I will keep investigating this
I have found the origin of the bug, I will work on the fix soon and it will be part of one of the coming REANA versions.
In any case, if you want a quick fix on your side, I see two options:
You can try to add "input_parameters": {}
to the parameters dict here in RECAST, but this will solve the issue only for newly-created workflows, and not for workflows that were run in the past with RECAST:
start_workflow(
- wflowname, self.auth_token, {"operational_options": operational_options}
+ wflowname, self.auth_token, {"operational_options": operational_options, "input_parameters": {}}
)
This bug also affects workflows executed via the GitLab integration
Thanks @mdonadoni! I really appreciate you taking a look at this. For me this really isn't a pressing issue, so I'm happy to wait for a fix and help test anything, it was more just that I noticed it while writing some documentation examples for RECAST.
There can be successful workflow runs on REANA with non-empty workspaces
that when the outputs are retrieved with
reana-client download
fail with
However, if particular files are targeted for download
these downloads succeed
It would be useful to get more user focused error messages if possible when downloads fail, as I'm not clear as to why this is happening.