Open avsastry opened 4 years ago
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
keep open
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
Same bug for me. Any update on it?
Maybe the bin path should be escaped with Escape.path()
in addition to Escape.variable()
: https://github.com/nextflow-io/nextflow/blob/2fb5bc07f2ad1309c9743b8675bb8003892e3eb7/modules/nextflow/src/main/groovy/nextflow/processor/TaskProcessor.groovy#L2090-L2091
Thanks @bentsherman, these headaches are all caused by the stupid decision made by the Dropbox team to include spaces in folder names. The solution (link below) provided by rwmorris solves the headache. Hope it helps someone else.
@bentsherman worth to give a try to it
Bug report
Expected behavior and actual behavior
I'm currently working within a Dropbox folder that is auto-named as "Dropbox (UCSD)". The presence of these parentheses seem to be properly accounted for in all cases, except when I'm trying to run a script from the "bin" folder. In the .command.run file, I see the following code:
It seems that the export call to use the "bin" directory doesn't backslash the parentheses and the spaces, resulting in a run error:
Steps to reproduce the problem
I can attach a working version if necessary
Program output