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…

Ok so I remove this and add all others to see what happens. However I dont know why it is the culprit? It has not been updated for a long time.

Plugins get broken if Discourse gets updated in a way that breaks the plugin. The other plugin you listed is maintained by a team member, so it’s somewhat more likely he’ll notice something’s wrong before other people.

Nope. It failed again. So I’m removing backup to dropbox this time.

But even if it is a broken plugin, why it would trigger rubbygem threshold? Its not making sense.

[Bild] hnaseri: But even if it is a broken plugin, why it would trigger rubbygem threshold? Its not making sense. I couldn’t figure that out either. I suspect that it’s unrelated. Are you still getting the rubygem error?

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?

[Bild] 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 I’ve …

Update failing due to rate limiting by RubyGems

Support

hnaseri (Hosein Naseri) 16. Juni 2017 um 22:51 21

I removed the backup to dropbox plugin and added all others and now it rebuilded without any error.

Thema		Antworten	Aufrufe
Unable to start discourse due to rubygems rate limiting Support	43	3787	14. Juni 2018
Rubygems: Too Many Requests problem returns! Support	16	3689	20. Februar 2019
The only solution I have found to workaround «429 Too Many Requests» failure from rubygems.org Support	4	2620	27. Oktober 2017
Rebuild Failed, please help! Self-hosting	7	1121	28. September 2022
Discourse won't rebuild Self-hosting	3	1144	7. August 2021

Update failing due to rate limiting by RubyGems

Verwandte Themen