Could not unpack Node, corrupt deflate stream

[garycourt]

I was trying to upgrade Node.js to v18.15.0 using Volta v1.0.8 under WSL1 running Ubuntu 20.04 LTS, and I get the following error:

Volta error: Could not unpack Node v18.15.0

Please ensure the correct version is specified.
Error details written to /home/user/.volta/log/volta-error-2023-04-03_18_54_22.854.log

The log file mentioned has these contents:

"node" "-v"
Volta v1.0.8

Could not unpack Node v18.15.0

Please ensure the correct version is specified.

Error cause: failed to unpack `/home/user/.volta/tmp/.tmpu2areJ/node-v18.15.0-linux-x64/include/node/openssl/bio_asm.h`

Error cause: failed to unpack `/home/user/.volta/tmp/.tmpu2areJ/node-v18.15.0-linux-x64/include/node/openssl/bio_asm.h`

Error cause: failed to unpack `node-v18.15.0-linux-x64/include/node/openssl/bio_asm.h` into `/home/user/.volta/tmp/.tmpu2areJ/node-v18.15.0-linux-x64/include/node/openssl/bio_asm.h`

Error cause: corrupt deflate stream

Any idea what's going on here? There's lots of storage space on this drive.

[garycourt]

After this error, I tried removing /home/user/.volta directory, re-installing Volta (v1.1.1), and installing Node.js again. I still get the same error.

I also tried an older version of Node.js (v18.14.2), and it also gives me the same error.

[ryanolee]

We ran into this on our CI pipeline. Looks like it could be an intermittent / network issue however @garycourt as it seems to be working for us now :eyes:

[garycourt]

I just gave it another try, and it also appears to be working for me now as well.

Thanks. Closing issue.

[harellevy]

same issue: Error cause: corrupt deflate stream nx cloud ci is unable to run because of this error... i get it twice a month minimum...

[garycourt]

I ran into this issue again today. I'm going to reopen this as I think someone looking into it is warranted.

[travis-jm]

Commenting because I'm starting to see this more frequently. Went from occasionally in CI/CD pipeline to team members reporting it to me.

[cskiwi]

Also having the same issues. very frustrating if you have to release something quickly and this just fails without any workaround

[chriskrycho]

I think this may be related to #1744 – if any of you folks are up for running a special lots-of-extra-tracing build I just created, see #1784 and follow the instructions under To Test there!

[chriskrycho]

This may also be related to https://github.com/sbstp/attohttpc/issues/84 – and if so, the issue is not specific to our choice of attohttpc, as that thread indicates; it shows up in reqwest and a few other libraries, and even in Go’s HTTP library. 😮‍💨 Will leave more notes here if/as I find things.