Cooldown is not updating

[Z2Flow]

I ran bundle update --all each day for the past eight days, and no updates occurred.
On RubyGems.org:

• json was updated on 8th March to 2.19.1
• json-schema was updated on 6th March to 6.2.0
• etc.

[indirect]

Thanks for reporting this! We were running into a bug while trying to handle the monthly rewrite/compaction of the gem info files. It should be fixed now. Please come back and let us know if you're still seeing this problem in the future.

[Z2Flow]

It's not fixed.
Again, for the past eight days, bundle update --all did not update any gem.

[simi]

Thanks for the report. We're looking into.

[indirect]

@Z2Flow hello, and thank you for your report. Can you help me understand how I can see the problem that you are seeing? I am investigating the cooldown index, and it appears to be running exactly 48 hours behind the main rubygems.org index.

What gem are you looking for in the cooldown index, that you aren't finding? How are you using the cooldown index? What does your Gemfile and Gemfile.lock look like? What commands are you running?

Here's how you can verify for yourself that the cooldown index is in fact working exactly as intended, by checking the cooldown index yourself:

❯ curl https://beta.gem.coop/cooldown/versions | tail -n 1
onebusaway-sdk 1.5.4 23c5957fbe5870d23ea3420e9b25adad

Okay, the newest cooled gem is onebusaway-sdk-1.5.4. Let's see when that gem was published:

❯ curl -s https://rubygems.org/api/v1/versions/onebusaway-sdk.json | jq '.[0].created_at' -r | ruby -rtime -e 'puts Time.parse(ARGF.read).localtime'
2026-03-24 23:53:59 -0700

That's almost exactly 48 hours ago. Here's the time now, for comparison:

❯ ruby -rtime -e 'puts Time.now.localtime'
2026-03-26 23:57:28 -0700

[Z2Flow]

Andre, Perhaps I am not understanding how this is supposed to work. In my Gemfile, the first line is this: source "https://beta.gem.coop/cooldown” When I execute `bundle update —all`, updated releases of gems, over a period of eight days, that are in my Gemfile are not updated. Changing the first line to this: source "https://gem.coop” and executing `bundle update —all` updates gems. What am I not understanding? Rob

…

On Mar 27, 2026, at 03:00, André Arko ***@***.***> wrote: indirect left a comment (gem-coop/gem.coop#35) <#35 (comment)> @Z2Flow <https://github.com/Z2Flow> hello, and thank you for your report. Can you help me understand how I can see the problem that you are seeing? I am investigating the cooldown index, and it appears to be running exactly 48 hours behind the main rubygems.org index. What gem are you looking for in the cooldown index, that you aren't finding? How are you using the cooldown index? What does your Gemfile and Gemfile.lock look like? What commands are you running? Here's how you can verify for yourself that the cooldown index is in fact working exactly as intended, by checking the cooldown index yourself: ❯ curl https://beta.gem.coop/cooldown/versions | tail -n 1 onebusaway-sdk 1.5.4 23c5957fbe5870d23ea3420e9b25adad Okay, the newest cooled gem is onebusaway-sdk-1.5.4. Let's see when that gem was published: ❯ curl -s https://rubygems.org/api/v1/versions/onebusaway-sdk.json | jq '.[0].created_at' -r | ruby -rtime -e 'puts Time.parse(ARGF.read).localtime' 2026-03-24 23:53:59 -0700 That's almost exactly 48 hours ago. Here's the time now, for comparison: ❯ ruby -rtime -e 'puts Time.now.localtime' 2026-03-26 23:57:28 -0700 — Reply to this email directly, view it on GitHub <#35?email_source=notifications&email_token=AZ5VGAZGOPCKCJEP7KWFWED4SYRI7A5CNFSNUABFM5UWIORPF5TWS5BNNB2WEL2JONZXKZKDN5WW2ZLOOQXTIMJUGA3DCMJUGA32M4TFMFZW63VHNVSW45DJN5XKKZLWMVXHJLDGN5XXIZLSL5RWY2LDNM#issuecomment-4140611407>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AZ5VGA2O7MLOR2XO6B5GCEL4SYRI7AVCNFSM6AAAAACWP2NZHKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHM2DCNBQGYYTCNBQG4>. You are receiving this because you were mentioned.

[indirect]

@Z2Flow Thanks for your reply! Since I don't have access to your Gemfile, I'm not able to reproduce the problem you describe. Can you provide a copy of your Gemfile, or at least a portion of your Gemfile, so I can try to debug?

[indirect]

Here's a bit of further investigation, trying to reproduce it with some gems chosen based on releases that are not yet cooled down:

First, look at the regular versions file, to find a gem we expect to not be in the cooldown:

❯ curl https://gem.coop/versions | tail
rcurses 6.3.2 eaa063e8ef7bf81e8d625031c8a8e51a
ruby-shell 3.6.20 c4b3d70745efc7f46fd408f155cdf3ab
rtfm-filemanager 8.2.4 940deefaee8888db0d9f85eb769dfa46
brrowser 0.1.4 e2488770e11bd1d40c2a424db3b54200

Looks like ruby-shell version 3.6.20 is a good candidate. It should not be present in the cooldown.

❯ bundle add ruby-shell
Fetching gem metadata from https://beta.gem.coop/cooldown/.
Resolving dependencies...
Fetching gem metadata from https://beta.gem.coop/cooldown/.
Fetching ruby-shell 3.6.19
Installing ruby-shell 3.6.19

As expected, 3.6.20 is missing from the cooldown, and only 3.6.19 is found.

Now, let's switch to the regular gem.coop server, and see if Bundler can find the new 3.6.20 version:

❯ echo 'source "https://gem.coop"' > Gemfile
❯ bundle update --all
Fetching gem metadata from https://gem.coop/.
Resolving dependencies...
Fetching ruby-shell 3.6.20 (was 3.6.19)
Installing ruby-shell 3.6.20 (was 3.6.19)
Bundle updated!

Looks like it worked! Switching sources from the cooldown to the main version caused a new version to appear and get successfully upgraded.

[Z2Flow]

André, Gemfile attached. Rob 

…

On Mar 28, 2026, at 17:27, André Arko ***@***.***> wrote: indirect left a comment (gem-coop/gem.coop#35) <#35 (comment)> @Z2Flow <https://github.com/Z2Flow> Thanks for your reply! Since I don't have access to your Gemfile, I'm not able to reproduce the problem you describe. Can you provide a copy of your Gemfile, or at least a portion of your Gemfile, so I can try to debug? — Reply to this email directly, view it on GitHub <#35?email_source=notifications&email_token=AZ5VGAZBWCFUTMN5DCNULWL4TA7TVA5CNFSNUABFM5UWIORPF5TWS5BNNB2WEL2JONZXKZKDN5WW2ZLOOQXTIMJUHA4DINBQG4ZKM4TFMFZW63VHNVSW45DJN5XKKZLWMVXHJLDGN5XXIZLSL5RWY2LDNM#issuecomment-4148844072>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AZ5VGA6GHBLYAVVS7GQSW7T4TA7TVAVCNFSM6AAAAACWP2NZHKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHM2DCNBYHA2DIMBXGI>. You are receiving this because you were mentioned.

[indirect]

@Z2Flow Hi Rob, unfortunately it seems the Gemfile attachment did not get picked up by the GitHub email gateway. I think that means you'll need to paste it into the GitHub website, or email it to me directly. If you could include your Gemfile.lock as well that would be very helpful.

[Z2Flow]

André, Email me with your direct email address please, and I will forward both. Cheers, Rob

…

On Mar 29, 2026, at 14:13, André Arko ***@***.***> wrote: indirect left a comment (gem-coop/gem.coop#35) <#35 (comment)> @Z2Flow <https://github.com/Z2Flow> Hi Rob, unfortunately it seems the Gemfile attachment did not get picked up by the GitHub email gateway. I think that means you'll need to paste it into the GitHub website, or email it to me directly. If you could include your Gemfile.lock as well that would be very helpful. — Reply to this email directly, view it on GitHub <#35?email_source=notifications&email_token=AZ5VGAZHGQFQBEOJWKGLH634TFRWNA5CNFSNUABFM5UWIORPF5TWS5BNNB2WEL2JONZXKZKDN5WW2ZLOOQXTIMJVGA3TMNJUGA3KM4TFMFZW63VHNVSW45DJN5XKKZLWMVXHJLDGN5XXIZLSL5RWY2LDNM#issuecomment-4150765406>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AZ5VGA372IB2OBHUX7ZKI2T4TFRWNAVCNFSM6AAAAACWP2NZHKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHM2DCNJQG43DKNBQGY>. You are receiving this because you were mentioned.

[indirect]

@Z2Flow Thanks for the offer! Fortunately, I was eventually able to recreate the problem you're seeing myself, on my own machine. It looks like there might be a bug in Bundler that means it doesn't correctly update the list of gems.

I carefully created a repo with a script to demonstrate the problem, where Bundler downloads an update for the file, records that it has updated the file, but does not actually update the file: https://github.com/indirect/bundler-cache-repro/blob/main/demo.sh.

In my testing, I was able to fix this problem by upgrading to the latest RubyGems and Bundler. Can you try running gem update --system and then gem install bundler, and let us know if that fixes your problem?

Thanks.

[Z2Flow]

André, In my case this isn’ the problem—I always keep current with the latest versions of RubyGems and Bundler. Cheers, Rob

…

On Mar 31, 2026, at 04:29, André Arko ***@***.***> wrote: indirect left a comment (gem-coop/gem.coop#35) <#35 (comment)> @Z2Flow <https://github.com/Z2Flow> Thanks for the offer! Fortunately, I was eventually able to recreate the problem you're seeing myself, on my own machine. It looks like there might be a bug in Bundler that means it doesn't correctly the list of gems. I carefully created a repo with a script to demonstrate the problem, where Bundler downloads an update for the file, records that it has updated the file, but does not actually update the file: https://github.com/indirect/bundler-cache-repro/blob/main/demo.sh. In my testing, I was able to fix this problem by upgrading to the latest RubyGems and Bundler. Can you try running gem update --system and then gem install bundler, and let us know if that fixes your problem? Thanks. — Reply to this email directly, view it on GitHub <#35?email_source=notifications&email_token=AZ5VGA6BE5TDSES23K5ECWL4TN6VXA5CNFSNUABFM5UWIORPF5TWS5BNNB2WEL2JONZXKZKDN5WW2ZLOOQXTIMJWGA4DINJVGEYKM4TFMFZW63VHNVSW45DJN5XKKZLWMVXHJLDGN5XXIZLSL5RWY2LDNM#issuecomment-4160845510>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AZ5VGAYQPQZWNNOXFKSF6JT4TN6VXAVCNFSM6AAAAACWP2NZHKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHM2DCNRQHA2DKNJRGA>. You are receiving this because you were mentioned.