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
Error when writting with ZBuilder::<Bgzf, _>::new().num_threads(8)...
#30
Comments
@mrvollger Sorry the delay in getting to this! I'll take a look later tonight or tomorrow. I don't see anything immediately wrong with your example code. |
Thanks so much for taking a look! I am having a hard time confirming this but I think it might have to do with the length of the sequences. I have run basically this code on short reads and never had a problem, but then I tried some contigs from assemblies and started to get this error. Thanks again! |
Yep, I have a fix incoming to gzp. It looks like when the Thank you for making this issue! I would not have run into this normally I don't think and missed it in all my test cases as well. |
Try the |
And thank you again for the issue! |
Just tried it and it got through the file and wrote all the records! Thanks! However, I do get this error/warning from samtools when I try to index the resulting file.
The index does appear to be created after this, and it is correct in this case, but it seems a little worrying. |
Good catch! The fix to make sure large writes were handled ended up skipping the EOF marker. As you noted it's not technically needed but the HTS suit of tools will complain if it isn't present. v0.9.5 has the fixes. Thanks for following up! |
Hello,
I am getting an error whenever I use
Zbuilder::<Bgzf, _>
with more than one thread and I am having trouble figuring out what is going wrong. Here is the error message I am getting:And here is some code and a test file that recreates this error for me:
Hete is the fasta file used in this example code:
large.test.fa.gz
Any help would be greatly appreciated!
Thanks!
Mitchell
The text was updated successfully, but these errors were encountered: