Open max-l opened 7 years ago
thank you so much for reporting this issue, @max-l! I was hoping to get to this soon, but couldn't as other things got in the way. I will be away for about a month, so no promises here but I will try to see whether I can squeeze a debugging/fixing session while I am away.
If this is urgent and has been blocking you, @ihodes might help you with the issue.
Let me know and sorry for the late feedback on this.
@armish thanks for the quick response, I've updated the JSFiddle to make sure it reproduces the bug
https://jsfiddle.net/srx4qecL/6/
I will be thrilled if @ihodes could look at the problem, but I understand that this is open source and you guys are already kind enough to have developed this awesome project !
One thing that would be awesome is if pileup would use webpack https://webpack.github.io/docs/
it would make and building and contributing to the project easier...
This JSFiddle illustrates the problem :
https://jsfiddle.net/maxl/srx4qecL/4/
In the chrome debug/network console, I see a few successful http requests to the bigbed, and eventually there is a request with the header : Range:bytes=9074145-NaN the server (nginx) then returns a 406 (Requested Range Not Satisfiable)
something causes pileup to emit a range with NaN ...
The same bigbed file works with other browsers (UCSC, dalliance)