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
Verwandte Themen
| Thema | Antworten | Aufrufe | Aktivität | |
|---|---|---|---|---|
| Unable to start discourse due to rubygems rate limiting | 43 | 3563 | 14. Juni 2018 | |
| Rubygems: Too Many Requests problem returns! | 16 | 3543 | 20. Februar 2019 | |
| The only solution I have found to workaround «429 Too Many Requests» failure from rubygems.org | 4 | 2577 | 27. Oktober 2017 | |
| Rebuild Failed, please help! | 7 | 1036 | 28. September 2022 | |
| Discourse won't rebuild | 3 | 1001 | 7. August 2021 |