Rubygems package registry checksum issue?

[sheck]

Select Topic Area

Bug

Body

I'm seeing issues with github package registry for private rubygems that look similar to #47659

As of 9am pacific today it appeared to be working, and around 11am pacific I noticed the same issue mentioned in the linked discussion. We're seeing it for multiple packages, both new and existing releases.

Bundler::HTTPError The checksum of /info/<GEM NAME> does not match the checksum provided by the server! Something is wrong (local checksum is "\"<SOME SHA>\"", was expecting "\"<A DIFFERENT SHA>\"")

[AMathews]

Can't provide any answers but you are not alone. We are experiencing it also. First noticed the problem over an hour ago when CI builds started failing for checksum mismatches.

[dnorth98]

Adding our voice to this issue which is breaking all our CI/CD builds. We have seen this before last year - maybe it's an annual occurrence now?

Last year's issue:
https://github.com/orgs/community/discussions/47659

[peterkarman1]

[AMathews]

Yeah, I guess I'll go outside or something...

[euge]

Having same issue here, also affecting CI/CD

[agirlnamedsophia]

Also seeing this issue, also affecting CI builds.

[njyrbecker]

Same here. CI builds and our dev environments all experiencing same issue for all packages hosted via github private repos. All were working fine yesterday.

[ethangarofolo-wsgr]

Same. Unable to pull gems.

[milesstanfield]

same. dead in the water

[Cookuricoo1]

Same

[substantial-kst]

Same

[scub]

Hello frenz

[tgnla]

:'(

[Gbarnett374]

😢

[iamwhil]

Creating more noise for this. 🔔

[rc-iwoodley]

Evan!

[iamwhil]

Evan!
It seems you landed here too!
What a fun day.

[emccullough-carerev]

Lol hey everyone! Glad we can get together and enjoy our inaccessible ruby gems!

[Jarvl]

Hey there peeps long time no see

[JamesMasonRC]

It's a reunion!

[euge]

For anyone here stuck, it seems bundle install --full-index is able to work around this issue. Definitely not the solution, but a temporary fix.

[BytewaveMLP]

Doesn't help in automated environments like Heroku, where you can't control the bundler flags in use. :(

[neebs12]

yes! this fixed it for us 😭

[smudge]

Worth noting that, as far as I can tell, this forces bundler to use the OLD gems APIs, which may not be desirable if the checksums are truly in a mismatched state (I'm not sure if the old APIs provide the same degree of cross-check/validation on gem install).

[minionOfZuul]

AFAICT this is more a problem with http caching digests (etags, etc) than with gem archive checksums.

[hoenth]

One more voice in the chorus. CI/CD builds busted, as well as Github Actions.

[hoenth]

We too were able to get CI/CD builds going again with bundle install --full-index. But not as easy to do the same with GH Actions

[kourylape]

Same. It fixes the build step, but still blocks other actions.

[kourylape]

+1

We too are seeing this.

[emccullough-carerev]

Hey Koury! Seeing all sorts of former coworkers here! 😂

[tinaheidinger]

Hello from GitHub Packages - we're looking into this!

Edit: We just deployed a fix, installing RubyGems packages should now work as expected

[kpaurora]

It seems to work again - at least on my end.

[areeseburnett]

We're still seeing the error.

[smudge]

Still seeing the error here as well.

[JWShuff]

Same here, wrangling through it, experimenting with the setup ruby action to see if we can work around it in the meanwhile.

[jeremiahrose]

Still happening here

[doanphuctam]

Still seeing checksum error.

[smudge]

I was just able to bundle install again.

Edit: Yup, seems to be working again across a few projects.

[emccullough-carerev]

Also seeing bundle installs work again in GitHub Actions at my org

[milesstanfield]

same. bundle installs working again at my org for dozens of ci/cd pipelines that were broken before