sha256sum mismatch

[zac-jacobson]

Version

16.17.1

Platform

No response

Subsystem

No response

What steps will reproduce the bug?

1. Observe https://nodejs.org/download/release/v16.17.1/SHASUMS256.txt
   In particular:

   2f459a64647db493da63c790ce368ad54f59f086d9f22f59c5018680420197b3  win-x64/node.lib
   

2. fetch the file in question

   curl  https://nodejs.org/download/release/v16.17.1/win-x64/node.lib --output node.lib
   

3. take the sha256sum of this file.

    ✗ sha256sum node.lib
    5792b101d69f08a082ef449a04835fc38574cb54cdc65014c4e78c628c9c2ff1  node.lib
   

How often does it reproduce? Is there a required condition?

every time

What is the expected behavior?

The expected result is that the values match.

What do you see instead?

They don't match, i.e.

local checksum 5792b101d69f08a082ef449a04835fc38574cb54cdc65014c4e78c628c9c2ff1 not match remote 2f459a64647db493da63c790ce368ad54f59f086d9f22f59c5018680420197b3

Additional information

We have been using node 16.17.1 since early January; only started seeing this issue today.

[zac-jacobson]

Work around: use v16.18.0

[richardlau]

Confirmed that if downloaded via https://nodejs.org/download/release/v16.17.1/win-x64/node.lib the checksum doesn't match.
However the file on our two servers does match the checksum -- it looks like the one fetched through the CloudFlare proxy is truncated/the wrong size:

PS C:\Users\ric\AppData\Local\Temp> ls .\node.lib* | select length, name

  Length Name
  ------ ----
 1526592 node.lib
12482388 node.lib.1
12482388 node.lib.2


PS C:\Users\ric\AppData\Local\Temp> Get-FileHash .\node.lib* | select hash,path

Hash                                                             Path
----                                                             ----
5792B101D69F08A082EF449A04835FC38574CB54CDC65014C4E78C628C9C2FF1 C:\Users\ric\AppData\Local\Temp\node.lib
2F459A64647DB493DA63C790CE368AD54F59F086D9F22F59C5018680420197B3 C:\Users\ric\AppData\Local\Temp\node.lib.1
2F459A64647DB493DA63C790CE368AD54F59F086D9F22F59C5018680420197B3 C:\Users\ric\AppData\Local\Temp\node.lib.2


PS C:\Users\ric\AppData\Local\Temp>

I'll try purging the CloudFlare CDN cache.

[richardlau]

@zac-jacobson Looks like clearing CloudFlare's cache has fixed it:

PS C:\Users\ric\AppData\Local\Temp> curl https://nodejs.org/download/release/v16.17.1/win-x64/node.lib -o node.lib.3
PS C:\Users\ric\AppData\Local\Temp> ls .\node.lib.3 | select length, name

  Length Name
  ------ ----
12482388 node.lib.3


PS C:\Users\ric\AppData\Local\Temp> Get-FileHash .\node.lib.3 | select hash,path

Hash                                                             Path
----                                                             ----
2F459A64647DB493DA63C790CE368AD54F59F086D9F22F59C5018680420197B3 C:\Users\ric\AppData\Local\Temp\node.lib.3


PS C:\Users\ric\AppData\Local\Temp>

[nedataghizadeh79]

This error message maybe because that the SHA-256 checksum of the downloaded file does not match the checksum provided by nodejs.org. This could be due to a number of reasons, including an issue with the download process, a problem with the file during transmission, or even a problem with the file on the nodejs.org server.

To resolve this issue, you can try downloading the file again, as it may have been corrupted during the initial download. You can also try downloading the file from a different source or mirror, to ensure that it is not a problem with the nodejs.org server. Additionally, you can try verifying the file's integrity using a different checksum algorithm, such as MD5 or SHA-1, to ensure that the file is not corrupted.

It's also possible that the issue is with the version of node.js that you are using. You may want to consider upgrading to a newer version to see if this resolves the issue.

[zac-jacobson]

@zac-jacobson Looks like clearing CloudFlare's cache has fixed it:

@richardlau Confirmed, the sha256sum matches this morning.

Thanks for the quick action!