-
Notifications
You must be signed in to change notification settings - Fork 5
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[RTD] Client Error 403 #558
Comments
@BaurzhanSakhariev added relevant code, but the program is still failing after receiving the 403 response. We need to compensate and improve. |
Others are observing the same, that the problem still occurs, even after adding the user agent header.
|
omg.
|
Implementing a fix according to the insights outlined above, there is a patch that we are also just probing. |
Fixing it like this apparently worked well. |
Problem
On our Jenkins, the rebuild all docs on RTD job started failing two weeks ago.
Evaluation
The program to rebuild all docs uses RTD's API heavily, as it iterates through all the projects and all their versions, and triggers a rebuild on each of them.
Observations
Up until recently, that regularly tripped the maximum number of concurrent builds at RTD, but those requests have been queued internally, and would run and resolve after a while. Now, however, this procedure yields a hard error.
Tip
Please note: It works well when invoked on an engineer's workstation, so it is most recently some rate limiting the Jenkins machine is flagged for.
Research
@BaurzhanSakhariev suggested:
Evaluation
The program that orchestrates the RTD API is indeed doing some amount of "hammering", and it also probably doesn't supply any user agent.
References
The text was updated successfully, but these errors were encountered: