I’ve got a couple builds failing due to rubygem rate limiting. (One at Digital Ocean, another at a COLO outside Boston). I thought that there was a recent update to the base Docker image that was supposed to mitigate this. It’s hard to find the error in the output too, since lots of stuff happens a…

We bumped the image quite recently … I think only 3 gems changed since the last base image. https://github.com/discourse/discourse/commits/master/Gemfile.lock

I’m still getting 218 requests. I commented out non-standard plugins. Then all plugins. I’ve done a git pull (which is superfluous given the number of builds I’ve attempted). It’s still doing 218 HTTP GETs.

[imagen] pfaffman: It’s still doing 218 HTTP GET s. To where :blush: what are the URLs, we need to figure out if this is just a general rubygems bug or this is legit discourse being out of data locally.

grep "HTTP GET" /tmp/build.log >/tmp/requests HTTP GET https://index.rubygems.org/versions HTTP GET https://index.rubygems.org/info/crass HTTP GET https://index.rubygems.org/info/mini_portile2 HTTP GET https://index.rubygems.org/info/activesupport HTTP GET https://index.rubygems.org/info/builder HT…

Yeah I don’t think there is anything we can do here, maybe @indirect has some tips here. I definitely don’t want to be hammering rubygems, but we got to do a bundle on bootstrap.

Is there an easy way to put a proxy in the middle and/or put some delay between the requests? Do you guys get all your stuff directly from rubygems?

I think to get into rubygems bad books you need to be mega offensive, we only bootstrap once for our internal deploys and reuse a base image so we never hit this.

Just to be super clear: those 255 requests are completely normal and correct, and I have never heard of anyone getting 429 rate limited for that kind of install. Our rate limits kick in for hundreds or thousands of requests per second for hours or days. If you think you’ve been wrongly rate limited,…

Thanks, @indirect . I have done lots of rebuilds on this machine, but only a couple hundred requests per manually started build (which look normal and expected to both you and me). Could some bad actor on the same network be the problem? (I know that I had this problem on another machine, but I can’…

You got to open a ticket on GitHub with RubyGems, its kind of a waste to do any more diagnostics here.

Rubygems: ¡el problema de demasiadas solicitudes ha vuelto!

Soporte

pfaffman (Jay Pfaffman) 30 Noviembre, 2018 19:04 14

Problem migrating polls: `integer out of range` (1000000000000)

Tema		Respuestas	Vistas
Update failing due to rate limiting by RubyGems Support	40	5795	18 Diciembre 2020
The only solution I have found to workaround «429 Too Many Requests» failure from rubygems.org Support	5	2573	27 Octubre 2017
Unable to start discourse due to rubygems rate limiting Support	45	3520	21 Diciembre 2020
Server in China can't reach rubygems.org so install fails Self-hosting	18	2495	8 Junio 2024
Error while trying to install Discourse Self-hosting	7	1739	26 Diciembre 2017

Rubygems: ¡el problema de demasiadas solicitudes ha vuelto!

Temas relacionados