CI Failure: Infrastructure issue with deb.nodesource.com (Hash Sum mismatch)

[petrus-v]

Description

Several CI jobs are currently failing during the dependency installation phase (apt-get update) specifically when fetching Node.js 20.x packages from NodeSource.

Observed Behavior

The apt-get update command fails with a "File has unexpected size" error. This usually indicates that the repository metadata is being updated or that a mirror is out of sync.

Error log snippet:

++ oca_list_external_dependencies deb
+ deps=libatlas-base-dev
+ '[' -n libatlas-base-dev ']'
+ apt-get update -qq
E: Failed to fetch https://deb.nodesource.com/node_20.x/dists/nodistro/main/binary-amd64/Packages.gz  File has unexpected size (13822 != 13998). Mirror sync in progress? [IP: 104.20.45.190 443]
   Hashes of expected file:
    - Filesize:13998 [weak]
    - SHA512:7e47e7196b8d4d8c27ad766e3573a5d767f98d89ccad7992f8a67b72205ee999c2e3ea9d03954c7af48ae095d07e9915a42779fbfce89e7155eb4ac94546ca76
    - SHA256:7ba93ae03f1737527679c96a497b789ae8f15fe94ba13e01294f6374957b31d9
    - SHA1:a3c5fe5523b5a76e015daa8020ec55026081066a [weak]
    - MD5Sum:1a00a6e03666a717d69771c968e8185c [weak]
   Release file created at: Thu, 05 Mar 2026 16:15:32 +0000
E: Some index files failed to download. They have been ignored, or old ones used instead.

Impacted Jobs

This is affecting multiple PRs across the OCA, including:

• PR: [19.0][MIG] account_loan + refactor account-financial-tools#2235
• Failed Job: Link to Action Job

Analysis

As far I understand, the remote server deb.nodesource.com is serving a Packages.gz file that does not match the size defined in its own Release file.

[petrus-v]

I re-launch the build, I guess the mirror get updated and synchronized in the mean time. I wonder if we can avoid such issue, I suppose it will be hard to achieve on our own as OCA organisation. I should probably contribute to the deb package registry mirror to make atomic update !...

If someone else agree with this analysis I'm fine to close this issue, at least we have it in the memory of this repo.