-
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] Backward-compatibility code trips documentation builds on downstream projects #553
Comments
@amotl is that related to the issue that you were discussing on Slack with @BaurzhanSakhariev? |
I don't think it is related to this specific issue. While it might be related to general refurbishments and modernizations at RTD, the other thing is related to networking and connectivity issues, and this one is related to Sphinx, so effectively, totally different domains. |
Ah, right, both are about rejected requests, possibly by rate limiting machineries. So, well, yeah, in this case both issues are probably connected. |
Maybe we need to tell them about the IP address of our Jenkins server? |
Hm, not necessarily. In this case, RTD is tripping itself: https://readthedocs.org/projects/crate/builds/26356993/ |
I've now also observed it happening on my workstation, when working on cratedb-guide in sandbox mode.
|
Problem
The recently added RTD backward-compatibility code in
src/crate/theme/vendor/rtd_compat/extension.py::manipulate_config
is highly problematic when it comes toTimeoutError
s, as it emits warnings then, which trip the build, because they are treated as errors in our setting.crate-docs-theme/src/crate/theme/vendor/rtd_compat/extension.py
Lines 14 to 131 in 0644241
References
The text was updated successfully, but these errors were encountered: