Skip to content
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

Using renamed symlinks as input BAM files doesn't work with --use_file_name option #152

Closed
mfoll opened this issue Feb 23, 2017 · 1 comment
Assignees
Milestone

Comments

@mfoll
Copy link
Member

mfoll commented Feb 23, 2017

This is a nextflow bug introduced after v0.22.1, see nextflow-io/nextflow#292. In the meantime a workaround it to use an older version of nextflow:

export NXF_VER=0.22.0
@mfoll mfoll added this to the v1.1 milestone Feb 23, 2017
@mfoll mfoll self-assigned this Feb 23, 2017
@mfoll mfoll changed the title Using renamed symlinks as input BAM files doesn't work with --use_file_name option Using renamed symlinks as input BAM files doesn't work with --use_file_name option Feb 23, 2017
@mfoll
Copy link
Member Author

mfoll commented Mar 15, 2017

Now solved with nextflow version 0.23.4, see nextflow-io/nextflow#292.

@mfoll mfoll closed this as completed Mar 15, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant