goenv icon indicating copy to clipboard operation
goenv copied to clipboard

goenv install fails on checksum issue in version 2.2.7

Open bo156 opened this issue 1 year ago • 2 comments
trafficstars

Hi, I encounterd an issue in which I've tried to use goenv install 1.21.0 on an amazon docker image (specifically we used public.ecr.aws/lambda/nodejs:18). After cloning your repository and running goenv install 1.21.0 it failed on a checksum issue with the logs:


[2024-10-08T13:32:44.310Z] │ 17.98 Inspect or clean up the working tree at

[2024-10-08T13:32:44.310Z] │ /tmp/go-build.20241008133127.192

[2024-10-08T13:32:44.310Z] │ 17.98 Results logged to /tmp/go-build.20241008133127.192.log

[2024-10-08T13:32:44.310Z] │ 17.98 

[2024-10-08T13:32:44.310Z] │ 17.98 Last 10 log lines:

[2024-10-08T13:32:44.310Z] │ 17.98 /tmp/go-build.20241008133127.192 /var/task

[2024-10-08T13:32:44.310Z] │ 17.98 

[2024-10-08T13:32:44.310Z] │ 17.98 checksum mismatch: Go Linux 64bit 1.21.0.tar.gz (file is corrupt)

[2024-10-08T13:32:44.310Z] │ 17.98 expected

[2024-10-08T13:32:44.310Z] │ d0398903a16ba2232b389fb31032ddf57cac34efda306a0eebac34f0965a0742, got

[2024-10-08T13:32:44.310Z] │ d0398903a16ba2232b389fb31032ddf57cac34efda306a0eebac34f0965a0742 

You can clearly see that the checksum is actually identical, yet the process failed.

The issue was solved by using version 2.2.6 (git checkout 2.2.6 && goenv install 1.21.0).

I also saw in the release notes of version 2.2.7 a commit with checksum in its name, which made me suspect this could be the cause.

bo156 avatar Oct 08 '24 14:10 bo156