-
Notifications
You must be signed in to change notification settings - Fork 62
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
Loading Annotation Track From S3, incorrect gzip header check #4431
Comments
Should add that the reference sequence loads fine, which is compressed and indexed. |
Adding more helpful error in browser inspector, with the hopes this helps :) autorunFeatureDensityStats.js:34 Error: problem decompressing block: incorrect gzip header check |
Doh! This was a coding issue. |
was it related to Content-Encoding:gzip headers by chance? this is something that i have often seen with these errors! |
Lol nope— bad coding on my part was pointing to a nonexistent uri! I went down the encoding rabbit hole for an hour before I realized it!
…--
[Logo Description automatically generated]
Dr. Jason R. Gallant
Associate Chair & Associate Professor
Department of Integrative Biology
Michigan State University
East Lansing, MI 48824
***@***.******@***.***>
office:517-884-7756
http://efish.integrativebiology.msu.edu<http://efish.integrativebiology.msu.edu/>
***@***.***?anonymous&ep=bwmEmailSignature>Click here to book time to meet with ***@***.***?anonymous&ep=bwmEmailSignature>!
________________________________
From: Colin Diesh ***@***.***>
Sent: Saturday, June 8, 2024 9:08:56 PM
To: GMOD/jbrowse-components ***@***.***>
Cc: Gallant, Jason ***@***.***>; State change ***@***.***>
Subject: Re: [GMOD/jbrowse-components] Loading Annotation Track From S3, incorrect gzip header check (Issue #4431)
was it related to Content-Encoding:gzip headers by chance? this is something that i have often seen with these errors!
—
Reply to this email directly, view it on GitHub<https://urldefense.com/v3/__https://github.com/GMOD/jbrowse-components/issues/4431*issuecomment-2156253504__;Iw!!HXCxUKc!wdOuiHVhlsCQjNY5KeYpNRd6lwi2TB1O4p00uaQCqYAam6Z5n3_Odz4Gh1LN1nsgjq9y-8hr95S7bOfuJWi9-8jH$>, or unsubscribe<https://urldefense.com/v3/__https://github.com/notifications/unsubscribe-auth/AAL4HSQMCWSQCNHUE7BQRF3ZGOTKRAVCNFSM6AAAAABJALO2S2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCNJWGI2TGNJQGQ__;!!HXCxUKc!wdOuiHVhlsCQjNY5KeYpNRd6lwi2TB1O4p00uaQCqYAam6Z5n3_Odz4Gh1LN1nsgjq9y-8hr95S7bOfuJW_qhq0y$>.
You are receiving this because you modified the open/close state.Message ID: ***@***.***>
|
interesting! i wonder why it didn't give the proper http error in that case, but glad you found the fix :) |
Hi @cmdcolin and team-- I'm trying to revamp our genome browser using react, hosted on S3. I've got a valid gff3 that has been sorted and tabixed, but when trying to load in the browser, I'm getting this issue. Any ideas about how to go about diagnosing/fixing?
Let me know if there is more info I can provide.
Cheers,
Jason
The text was updated successfully, but these errors were encountered: