Unable to modify files during packing due to "size mismatch"
See original GitHub issueThe readme file mentions using mapStream
during pack.entry
, but any transformation on the stream that alters the size of the contents results in “size mismatch” error, thrown from tar-stream here https://github.com/mafintosh/tar-stream/blob/bbb3e91a44fde7bdb3d179e27afdaa4b08fa74ac/pack.js#L174.
The error is silent. Unless debugging logs are added to onnextentry
function of tar-fs, the error manifests as the stream simply freezing.
Is there a way to get around this?
Issue Analytics
- State:
- Created 7 years ago
- Comments:12 (4 by maintainers)
Top Results From Across the Web
Critical error: Serial size mismatch - Unreal Engine Forums
Hi there! Seems like the file size changes during the cooking/packing process. On the screenshot attached, the left is project Content folder ...
Read more >Failed to fetch because of size mismatch error while upgrading
Try sudo apt-get update --fix-missing. in terminal and then sudo apt-get upgrade.
Read more >MD5 error occurs when downloading the Host On-Demand ...
A file size of '0' indicates a problem on the server. Any other file size discrepancy can be caused by several circumstances.
Read more >Size Mismatch - Can I fix this? - MacRumors Forums
The installer is expecting a certain file size and since the upload size is slightly less there is a size mismatch - hence...
Read more >apt update in debian fails due file size mismatch - Vivaldi Forum
Mirror sync in progress? [IP: 151.101.193.91 443] Fetched 833 B in 0s (1,781 B/s) Reading package ...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Will merge a PR that makes the readme better for this
This can also happen if you are writing into the same folder that is being
tar
ed. I changed my tar path and it worked just fine.