Closed baptisteArno closed 3 weeks ago
Manually install the version works proto install node 20.17
Sometimes when this error occurs, it's not actually because the hash is wrong, but because the files were partially downloaded but interrupted halfway through (ctrl+c'd maybe).
If you delete the files ~/.proto/temp/node/20.17.0/node-v20.17.0-darwin-arm64.tar.xz
and ~/.proto/temp/node/20.17.0/SHASUMS256.txt
, and then the install works, that's probably what caused it. I need to figure out a way to detect this, but capturing interruptions is difficult.
Also, it looks liek the hash it generated was f446e6a5dedca2e5d337bd8d81cdcfff7b66cadeeb9420011fd2648e8ec401df
. You can open the SHASHUMS256.txt
file and see what hash they have.
After looking at the logs, I think that's what happened:
[DEBUG 21:35:40.229] proto_core::tool Tool already downloaded, continuing tool="node"
Just tried with another version and I can't reproduce the bug. Maybe I misclicked when it was downloading at first like you say :)
Cool.
I think I'll have the install just ignore previous downloads to avoid this scenario.
What version?
0.40.2
Which command?
No response
What happened?
When running
node --version
orpnpm --version
in project that has non installed version requirements of those execs, it correctly auto download them but then I have aproto::verify::invalid_checksum
errorTrace logs?
Operating system?
MacOS
Architecture?
arm64