-
Notifications
You must be signed in to change notification settings - Fork 424
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
Sanitize path #1568
Comments
For context, the bug is that sometimes the path is resolved to include a double slash. This breaks certain filesystems: e.g.
Using file operations will solve this: https://www.nextflow.io/docs/latest/script.html#opening-files Options: |
After the recent dicussions, do we still want to fix this here or rather wait for a nextflow fix? This applies to virtually all nf-core pipelines and how they specify the outdir in modules.config Related issue: #1580 |
fixed by nextflow as far as I can tell. Any remaining issues are in nf-validation |
Line 31 in ae4dd11
Using test profile:
|
Description of the bug
params.outdir + "/path/output/"
->
file(params.outdir + "/path/output/").toUriString()
Command used and terminal output
No response
Relevant files
No response
System information
No response
The text was updated successfully, but these errors were encountered: