-
-
Notifications
You must be signed in to change notification settings - Fork 95
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: Invalid tar header. Maybe the tar is corrupted or it needs to be gunzipped? #158
Comments
Can you add a proper test with the tar that fails as a fixture, without the fetch and stream wrappers |
I don't really know what's the issue so I can't develop a proper fixture for it, but here you go: https://gitea.nulo.in/Nulo/tar-stream (uploaded to a self-hosted repo because GitHub doesn't allow LFS in forks...) |
I'm encountering a similar (but maybe completely different?) issue. I'm using For me, Line 307 in 03da589
Replacing that line with return parseInt(Buffer.from(val).toString('utf-8', offset, end), 8) and adding const {Buffer} = require('buffer'); to the top of the file seems to fix the issue. Edit: Upstream issue: feross/buffer#329 |
I ran into a similar problem as @personalizedrefrigerator and ended up submitting a PR for it: #164 |
repro:
The text was updated successfully, but these errors were encountered: