Error: invalid signature: 0x7d70fadf
See original GitHub issueI’ve got a script that downloads zips from github and unzips them into a temporary directory.
On machines with 4 gigs or less, it’s crashing on any file over 2 megs.
https://github.com/gomobile/sample-counting-beads - that is a sample that I’m getting the zip from.
Below is the message I am seeing. The signature changes each time, but it happens on mac, linux, and windows. On my macbook pro with 8 gigs of ram, it works fine (I’ve pulled down 20 meg files).
Error: invalid signature: 0x7d70fadf
at C:\my_project\node_modules\unzip\lib\parse.js:1:1127
at process._tickCallback (node.js:351:13)
Issue Analytics
- State:
- Created 10 years ago
- Comments:6
Top Results From Across the Web
Error "Invalid Signature [ID=0xc72d0006]" after firmware ... - IBM
After a firmware upgrade, a condition was discovered where the Network IPS LMI would display a sensor down warning.
Read more >Error "Invalid Signature" while downloading programs.
Click on "Advanced" tab. d. Scroll down to the Security section, check the Allow software to run or install even if the signature...
Read more >what does Error: Invalid Signature mean in moveit automation?
Most likely it's either AV on the target host or SCCM endpoint protection. Check the logging for moere detail, see if you get...
Read more >Error: Invalid signature - LearnSci Help Desk
If you see an error message containing the words "invalid signature" when opening a Learning Science resource it could be caused by one...
Read more >Studio 5000 : Compiler Error 'invalid Signature ID. Reseal ...
The project cannot be verified and this error is shown in the Errors pane: Error: MyAOI: Invalid Signature ID. Reseal instruction to resolve ......
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 Free
Top 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
FYI. in case anyone still need the solution: patches in http://github.com/glebdmitriew/node-unzip-2 just resolved the problem.
Getting such error some times on extracting file via ftp. Solution was to subscribe stream to ‘error’ event. Simplified to fs, like
Should work, if you get this error not permanent, but from time to time