Installing packages is failing in Github Actions

When I run sudo apt update I am now seeing the following 100% of the time.

Run sudo apt update

`…
Err:25 https://packages.microsoft.com/ubuntu/20.04/prod focal/main amd64 Packages
File has unexpected size (73402 != 73160). Mirror sync in progress? [IP: 104.42.185.173 443]
Hashes of expected file:

  • Filesize:73160 [weak]
  • SHA512:782bf0315c8de4314049e599009430053b75a5015491b3d383b09239fcf31857d52bac3399cef8e813f7b2131dce09b03eaf89d79c5ebd2849402cee7aa9d228
  • SHA256:dbf4bf81b4a0a17dae53f2aff3edd4cf5bb1dcd5dcd216ce5c5c8ab7c507a26a
  • SHA1:0e1b47276cae4168a08d8fd981891d4773f053b9 [weak]
  • MD5Sum:0fcf3ed335cd4efde65300bb48c05afe [weak]
    Release file created at: Sat, 15 May 2021 00:38:08 +0000
    Fetched 4467 kB in 1s (4534 kB/s)
    Reading package lists…
    E: Failed to fetch https://packages.microsoft.com/ubuntu/20.04/prod/dists/focal/main/binary-amd64/Packages.bz2 File has unexpected size (73402 != 73160). Mirror sync in progress? [IP: 104.42.185.173 443]
    Hashes of expected file:
    - Filesize:73160 [weak]
    - SHA512:782bf0315c8de4314049e599009430053b75a5015491b3d383b09239fcf31857d52bac3399cef8e813f7b2131dce09b03eaf89d79c5ebd2849402cee7aa9d228
    - SHA256:dbf4bf81b4a0a17dae53f2aff3edd4cf5bb1dcd5dcd216ce5c5c8ab7c507a26a
    - SHA1:0e1b47276cae4168a08d8fd981891d4773f053b9 [weak]
    - MD5Sum:0fcf3ed335cd4efde65300bb48c05afe [weak]
    Release file created at: Sat, 15 May 2021 00:38:08 +0000
    E: Some index files failed to download. They have been ignored, or old ones used instead.
    Error: Process completed with exit code 100.`
2 Likes

Same here! This seems to be a problem Github-wide if you use their apt repos.

It seems to have resolved, but it would be nice if there was a better way to report a GH outage that they aren’t aware of.

Hey all,

Our Community forum here does have integration with our public status page and should dynamically post a banner to the main Community page.

For this Actions impact, the public details are listed, here:

For how to let us know you are experiencing what might be a site-wide interruption of service, posting here is a great step.

Otherwise, following our public status page will be the best way to find out if a problem might be unique or more widespread.

Thanks to you all for letting us know your experience here!

:bow: