Gem hash difference

[ghost]

I'm seeing a similar issue to rubygems/bundler#5332

Basically if I run gem fetch faraday_middleware -v 0.12.1 then shasum -a256 faraday_middleware-0.12.1.gem the hash I see (021dc9fd7e7b6de1bc394637c7b8214a1f8b2d1407867e5239c90b5405a31ff3) is different than the one on rubygems.org (06764c0b5e7f10a5efeae501da2c825f0e479969c8ca9b585583fd6546ba63df).

Republishing seemed to help last time. Can we try again?

As a side note, seems a little odd that it happens to this gem twice but is a rare thing?

[beloso]

I am having the same problem:

(The expected SHA256 checksum was "06764c0b5e7f10a5efeae501da2c825f0e479969c8ca9b585583fd6546ba63df", but
the checksum for the downloaded gem was "021dc9fd7e7b6de1bc394637c7b8214a1f8b2d1407867e5239c90b5405a31ff3".)

[wojtha]

Ran into this as well, it seems to be caused by Travis CI publishing process as @sonalkr132 wrote:

I believe we know why this is happening. You are using Travis to push gems. Travis ends pushing the gem from all the jobs. One of them pass and rest fail. Because of the race condition in Api::V1::RubygemsController#create, we end up with incorrect checksums.

[adellibovi]

Exactly same problem here too
(More info: The expected SHA256 checksum was "06764c0b5e7f10a5efeae501da2c825f0e479969c8ca9b585583fd6546ba63df", but the checksum for the downloaded gem was "021dc9fd7e7b6de1bc394637c7b8214a1f8b2d1407867e5239c90b5405a31ff3".)

[zero3nna]

Same problem for me if our Jenkins tries to bundle update

[iMacTia]

I'm sorry guys this happened again, I thought this was fixed limiting the rubygems release to only some jobs. Clearly the fix is not working as expected, but it worked just fine for v0.12.0.
I'll try to get this fixed ASAP

[iMacTia]

this is the condition I'm referring to, it should publish on Rubygems ONLY for the "2.4.0 / Gemfile" combination.
I'll keep looking around for a reason but any suggestion is really welcome

[iMacTia]

I'll try to apply the fix from this rubygems/rubygems.org#1551 (comment) and re-release

[iMacTia]

v0.12.2 on its way, finger crossed 🤞

[adellibovi]

Thanks a lot @iMacTia and absolutely no need to be sorry about this :)

[iMacTia]

Thanks @adellibovi, and just to be extra safe I'm running tests for ruby 2.4.0 only against the base Gemfile. I don't want to see race conditions anymore!

[iMacTia]

faraday_middleware 0.12.2 released

A quick gem install faraday_middleware successfully installed v0.12.2 so hopefully this is now fixed 👍