Unable to read large BAM header which spans multiple bgzf blocks about igv.js HOT 2 CLOSED

Jonathan, could you attach a small test bam that reproduces the
problem? You can also email it to me directly, or let me know where I
can fetch it.

bamReader readHeader needs some refactoring to handle larger BAM
header content.

It was not sufficient to simply increase the number of bytes initially
read, as only a single bgz block was uncompressed during processing
despite a larger range fetched by the dataLoader.

Our BAM files for Proton have one @rg https://github.com/RG entry
per processed tile (96) and many @co https://github.com/CO comments
to capture parameters used to generate the files, making for rather
large BAM headers.

—
Reply to this email directly or view it on GitHub
#7.

from igv.js.

Jonathan, I think this is fixed. Could you test on one of your files, and close if it works?

from igv.js.