This issue still exists. “Talking to rubygems” cannot be an option. If an application is hitting a ratelimit by 3rd party, the application has to take care of building requests not exceeding the limits and/or to retry failed downloads after a safe period until the downloads are done.
thabbs
(Thomas Abraham)
32
Argomenti correlati
| Argomento | Risposte | Visualizzazioni | Attività | |
|---|---|---|---|---|
| Unable to start discourse due to rubygems rate limiting | 43 | 3563 | Giugno 14, 2018 | |
| Rubygems: Too Many Requests problem returns! | 16 | 3543 | Febbraio 20, 2019 | |
| The only solution I have found to workaround «429 Too Many Requests» failure from rubygems.org | 4 | 2577 | Ottobre 27, 2017 | |
| Rebuild Failed, please help! | 7 | 1036 | Settembre 28, 2022 | |
| Discourse won't rebuild | 3 | 1001 | Agosto 7, 2021 |