We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
The combination of these two code chunks...
tool-NFTest/nftest/NFTestENV.py
Line 23 in d096b96
tool-NFTest/nftest/NFTestCase.py
Lines 103 to 105 in d096b96
... and python's behavior of stripping leading ./s from paths...
./
In [2]: Path("./") / "foo" Out[2]: PosixPath('foo')
... results in passing bare relative paths for the --output_dir argument, which triggers uclahs-cds/pipeline-Nextflow-config#59 for me:
--output_dir
NXF_WORK=././test/work nextflow run ./main.nf -c /hot/code/nwiltsie/pipelines/pipeline-align-DNA/test/global.config -c ./test/a_mini_n2-picard.config --output_dir a_mini_n2-picard
We should resolve all of those relative paths before launching Nextflow.
The text was updated successfully, but these errors were encountered:
Agreed, also building on this, we should resolve all paths for the config files in the Nextflow run command
Sorry, something went wrong.
No branches or pull requests
The combination of these two code chunks...
tool-NFTest/nftest/NFTestENV.py
Line 23 in d096b96
tool-NFTest/nftest/NFTestCase.py
Lines 103 to 105 in d096b96
... and python's behavior of stripping leading
./
s from paths...... results in passing bare relative paths for the
--output_dir
argument, which triggers uclahs-cds/pipeline-Nextflow-config#59 for me:NXF_WORK=././test/work nextflow run ./main.nf -c /hot/code/nwiltsie/pipelines/pipeline-align-DNA/test/global.config -c ./test/a_mini_n2-picard.config --output_dir a_mini_n2-picard
We should resolve all of those relative paths before launching Nextflow.
The text was updated successfully, but these errors were encountered: