-
Notifications
You must be signed in to change notification settings - Fork 660
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
Staging input files in a subfolder changes their names when they are symlinks #292
Labels
Comments
It seems to be related to #222, as the output is correct with a version before this has been fixed (but symlinks are not resolved of course):
|
pditommaso
added a commit
that referenced
this issue
Feb 23, 2017
Good shot! I've just uploaded |
I just checked and it is working as expected. Thanks for the quick fix! |
Released with version |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
When input files are symlinks (like
titi.txt
in the following example) pointing to a file with a different name (tata.txt
in the example) AND we ask nextflow to stage this file as an input in a subfolder (TXT/
here), the new link created by nextflow in this folder inwork
is renamed with the name of the symlink target (tata.txt
here).Here is a replicable toy example of the bug. My current environment:
Note here
titi.txt -> /data/follm/tata.txt
. The nextflow script causing the bug:The output when running the script:
Note that here
tata.txt -> /mnt/beegfs/follm/tata.txt
while the file was originally namedtiti.txt
(note that in my system/data -> /mnt/beegfs
, so this is correctly resolved).Simply changing
file 'TXT/*' from txt
tofile txt
or evenfile '*' from txt
returns the correct output (at least what I am expecting...):Note here
titi.txt -> /mnt/beegfs/follm/tata.txt
.The text was updated successfully, but these errors were encountered: