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
I have just come across this behavior testing out mappy on a genome file that I had accidentally moved. mappy.Aligner is able to initialize with a non-existent file, but any operation (aside from the map function) on that alignment object causes a segmentation fault (seq or seq_names).
It would be nice if the Aligner object raised a python error on a non-existent file, but raising a catchable error for the seq and seq_names functions would be useful as well.
The following code reproduces this error (assuming foo.fasta does not exist):
I have just come across this behavior testing out mappy on a genome file that I had accidentally moved.
mappy.Aligner
is able to initialize with a non-existent file, but any operation (aside from themap
function) on that alignment object causes a segmentation fault (seq
orseq_names
).It would be nice if the
Aligner
object raised a python error on a non-existent file, but raising a catchable error for theseq
andseq_names
functions would be useful as well.The following code reproduces this error (assuming
foo.fasta
does not exist):The text was updated successfully, but these errors were encountered: