You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If trying to use augur align with an alignment with a space in the filename (e.g. E30 FLs.FST), this is passed to mafft with the space, but without quotes, and breaks mafft.
Fixes this. However, I imagine this kind of problem could happen other places here (what if reference file has a space? Output file?) and in other augur commands (tree?). Dunno if it would be better to do something more comprehensive, or just fix this for now?
The text was updated successfully, but these errors were encountered:
The best way to fix this issue is to run commands without using the shell by providing a list of command arguments (argv) instead of a command string.
The next best way is to shell-quote all the variables interpolated into command strings using shlex.quote. However, this is more verbose for the caller and prone to being forgotten by the programmer, so it's less robust.
It appears this specific problem was addressed in #422. There is a similar problem which could now occur when providing a filename which includes spaces to the --existing-alignment argument of augur align. This issue is addressed in #452.
If trying to use
augur align
with an alignment with a space in the filename (e.g.E30 FLs.FST
), this is passed to mafft with the space, but without quotes, and breaks mafft.The call:
Give this error:
And also makes a super weird log file. Nothing points to the fact the space in the file name is the error.
Renaming file to remove the space fixes the error. Also seems like changing line 97 in
align.py
:to have single quotes around the input file name
Fixes this. However, I imagine this kind of problem could happen other places here (what if reference file has a space? Output file?) and in other
augur
commands (tree
?). Dunno if it would be better to do something more comprehensive, or just fix this for now?The text was updated successfully, but these errors were encountered: