Hello. I wanted to update my discourse for new commits, it did fail. Then I rebuild app, it also failed with the following error. Any Idea? FAILED -------------------- Pups::ExecError: cd /var/www/discourse && su discourse -c 'bundle exec rake db:migrate' failed with return #<Process::Status: pid 1…

[afbeelding] hnaseri: I removed the backup to dropbox plugin and added all others and now it rebuilded without any error. In that case, @Falco might want to have a look at the dropbox plugin.

If you get rate-limited by rubygems, you need to talk to rubygems. They explain how in their rate-limiting documentation . We can do absolutely nothing to help with rate-limiting problems. (This doesn’t just apply to the OP; everyone giving advice on this problem any time it occurs needs to refe…

It doesn’t make sense to me why in such situations we need to talk to rubygems. We are installing/Updating something that passes their thresholds. So I think their response would simply be for us to check the plugins we are trying to install. Am I right?

[afbeelding] mpalmer: If you get rate-limited by rubygems, you need to talk to rubygems. They explain how in their rate-limiting documentation. We can do absolutely nothing to help with rate-limiting problems. That’s what I think too, but this has been coming up lately, and I’m using a host…

[afbeelding] hnaseri: It doesn’t make sense to me why in such situations we need to talk to rubygems. Because they’re the ones rate-limiting your requests. [afbeelding] hnaseri: We are installing/Updating something that passes their thresholds. So I think their response would simply be f…

I’ve got an idea now. I’ll see if I can figure out how to ask ruby gems about the problem. If I find out anything useful, I’ll let you know. :wink:

[afbeelding] pfaffman: I’ve got an idea now. I’ll see if I can figure out how to ask ruby gems about the problem. If I find out anything useful, I’ll let you know. :wink: @pfaffman – Why not work with @hnaseri – I recall @11145 having an issue as well – maybe the three of you gather: outputs…

Is there any update on this issue @pfaffman ?

I’ve not heard back from them.

Has anybody solved the problem? I have the same issue: every attempt to run ./launcher rebuild <container> fails with the «429 Too Many Requests» from rubygems.org : [01] Here is the only solution I have found: The only solution I have found to workaround «429 Too Many Requests» failure from ruby…

Update failing due to rate limiting by RubyGems

Ondersteuning

pfaffman (Jay Pfaffman) 12 juni 2018 om 00:37 39

It sounds like this might be a solution

Topic		Antwoorden	Weergaven
Unable to start discourse due to rubygems rate limiting Support	43	3574	14 juni 2018
Rubygems: Too Many Requests problem returns! Support	16	3562	20 februari 2019
The only solution I have found to workaround «429 Too Many Requests» failure from rubygems.org Support	4	2580	27 oktober 2017
Rebuild Failed, please help! Self-hosting	7	1053	28 september 2022
Discourse won't rebuild Self-hosting	3	1018	7 augustus 2021

Update failing due to rate limiting by RubyGems

Gerelateerde topics