Skip to content
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

Closed
jasongallant opened this issue Jun 8, 2024 · 6 comments
Closed

Loading Annotation Track From S3, incorrect gzip header check #4431

jasongallant opened this issue Jun 8, 2024 · 6 comments

Comments

@jasongallant
Copy link

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

Error loading source map, showing raw stack trace below:
Error: problem decompressing block: incorrect gzip header check
@http://localhost:3000/static/js/bundle.js:63145:22
unzip@http://localhost:3000/static/js/bundle.js:63113:22
@http://localhost:3000/static/js/vendors-node_modules_gmod_tabix_esm_index_js.chunk.js:856:85
@jasongallant
Copy link
Author

Should add that the reference sequence loads fine, which is compressed and indexed.

@jasongallant
Copy link
Author

Adding more helpful error in browser inspector, with the hopes this helps :)

autorunFeatureDensityStats.js:34 Error: problem decompressing block: incorrect gzip header check
at unzip (unzip-pako.ts:51:1)
at TabixIndex._parse (tbi.ts:49:1)
at async TabixIndex.getMetadata (indexFile.ts:42:1)
at async TabixIndexedFile.getReferenceSequenceNames (tabixIndexedFile.ts:324:1)
at async MainThreadRpcDriver.call (MainThreadRpcDriver.js:30:1)
at async loadRefNameMap (assembly.js:52:1)

@jasongallant
Copy link
Author

Doh! This was a coding issue.

@cmdcolin
Copy link
Collaborator

cmdcolin commented Jun 9, 2024

was it related to Content-Encoding:gzip headers by chance? this is something that i have often seen with these errors!

@jasongallant
Copy link
Author

jasongallant commented Jun 9, 2024 via email

@cmdcolin
Copy link
Collaborator

cmdcolin commented Jun 9, 2024

interesting! i wonder why it didn't give the proper http error in that case, but glad you found the fix :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants