Closed antoni-szych-rtbhouse closed 9 months ago
This is true for the oldest nodejs16 builds too. More recent ones are okay. But I haven't investigated what is the first release to be installable.
I'm also seeing this behavior with the 20_x releases:
Get:10 https://deb.nodesource.com/node_20.x nodistro/main amd64 Packages [2,961 B] Err:10 https://deb.nodesource.com/node_20.x nodistro/main amd64 Packages File has unexpected size (2795 != 2961). Mirror sync in progress? [IP: 104.22.5.26 443] Hashes of expected file:
@jdmartin Node.js v20 errors are due to a new version being released and may appear while the cache is being updated.
Gotcha. As it happens, I waited until now, ran apt-get clean, and then the upgrade proceeded as expected. :)
@antoni-szych-rtbhouse we will do an investigation into what is happening
Please note that this issue is not reproducible anymore with any of the examples I provided previously:
18.14.0-1nodesource1
18.14.1-1nodesource1
18.14.2-1nodesource1
18.15.0-1nodesource1
18.16.0-1nodesource1
Now their size matches the size specified in the index file and the installation succeeds without any issues.
Example headers:
curl -v https://deb.nodesource.com/node_18.x/pool/main/n/nodejs/nodejs_18.14.0-1nodesource1_amd64.deb
* Trying 2606:4700:10::ac43:acd:443...
* Connected to deb.nodesource.com (2606:4700:10::ac43:acd) port 443 (#0)
...
< HTTP/2 200
< date: Wed, 11 Oct 2023 09:19:11 GMT
< content-type: application/octet-stream
< content-length: 29017700
< x-amz-id-2: LDjoaPVNoOmJIgopU9FeF35FigAOmpVk/BFcEZtEEbHinyXJwo0HY+GNDZhVENeJkhUk1+ublx8=
< x-amz-request-id: 1EBVFEHZ5NSKMB6E
< x-amz-meta-md5: 2905962bef8a243cad3c378cca5679a9
< last-modified: Mon, 18 Sep 2023 23:04:07 GMT
< etag: "2905962bef8a243cad3c378cca5679a9"
< cache-control: max-age=14400
< cf-cache-status: MISS
< accept-ranges: bytes
< server: cloudflare
< cf-ray: 8146051b79e135ba-WAW
Maybe the last-modified: Mon, 18 Sep 2023 23:04:07 GMT
will be helpful in case you would like to investigate this further. Otherwise please feel free to close this issue as not reproducible anymore (at least for node 18.x).
It seems this might be occurring again with the nodejs_20.9.0 release. Specifically the Packages.bz2
file.
31.98 E: Failed to fetch https://deb.nodesource.com/node_20.x/dists/nodistro/main/binary-amd64/Packages.bz2 File has unexpected size (4070 != 3613). Mirror sync in progress? [IP: ...]
31.98 Hashes of expected file:
31.98 - Filesize:3613 [weak]
31.98 - SHA512:2baf8ce0fd06ccf978d7e73b1adc6fa8390dc5ff7942ab2d5b89903460ec9e188203851f12877cedcac57fc7047224194e64b772de199d733f72dbfb10b68317
31.98 - SHA256:fba8379cf729d58a5b6adab466a20a4e5bcef6a4e8dc584fe7c2a33f568cb062
31.98 - SHA1:b2ed6eae7078e1c3644014c3afb9f6e2aea85f33 [weak]
31.98 - MD5Sum:a9aebf4761f08a52bda814a67963e487 [weak]
31.98 Release file created at: Tue, 24 Oct 2023 15:16:00 +0000
31.98 E: Some index files failed to download. They have been ignored, or old ones used instead.
Failing for other versions as well: (is there a workaround?!)
E: Failed to fetch https://deb.nodesource.com/node_18.x/pool/main/n/nodejs/nodejs_18.17.1-deb-1nodesource1_amd64.deb 404 Not Found [IP: 104.22.5.26 443]
This issue was due to a cache corruption, but as of today everything is working properly.
Describe your bug Unexpected file size of Node binaries.
Distribution Information:
Node Version:
To Reproduce Steps to reproduce the behavior:
Actually, the same is reproducible with:
However it's working fine with:
Expected behavior
Installation success.
Screenshots
so the hashes are correct, but the filesize is different. Maybe that's an issue with
apt
or something? Let's try sending a direct HTTP request:see the
content-length: 28609760
? It was supposed to be29017700
according to the index file (see second line from the bottom):Additional context
None that seems relevant.