-
Notifications
You must be signed in to change notification settings - Fork 237
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
Sphinx documentation is broken #932
Comments
I would be against downgrading sphinx (upgrading Sphinx is a PIA). I think we should just figure out what is wrong in the process and fix with current versions or newer. Totally agree we need better CI/CD checking here and need a way to verify that readthedocs is actually getting updated (since even with better Nornir testing it is pretty easy for readthedocs to be failing and for no one to realize it). Probably should expand the allowed maintainers in readthedocs so it isn't entirely David (my RTD username is "ktbyers"). It looks like I am not currently a maintainer. |
Note, RTD changed some things in October of last year which might also cause other breakage. See this NAPALM issue for reference: |
Nevermind on that last item...it looks like I already fixed that (prior to it breaking last August). |
Regarding upgrading Sphinx being a PITA, an issue here could be that the version was bumped without doing anything else which caused these failures. In that sense it's not property upgraded now. |
It looks like the following API has changed:
I should be home in 2 hours and can look for a fix and create a PR. |
As I am to blame for the PITA situation, I created a PR to fix the documentation build. |
I don't think we need to assign blame, the real problem was that the CI job was disabled for so long. I think the real problem now is that it's completely broken and as such it would be better to have it in the current state even if there are errors. Having said that this is what the |
I started with fixing the warnings but not finished yet: #934 |
I added ktbyers to the list of maintainers and change the "latest" branch to point to I am happy to add more people as RTD maintainers if you can't see the build logs |
Build issue is a Python mismatch (i.e. Sphinx using one Python / Poetry using a different one). Attempt to fix here: |
Okay this PR was able to fix the readthedocs build issue: GH Webhook to RTD is still not working so looking into that. |
Okay, webhook to RTD looks to be working again...I had to add a secret from RTD into GitHub on the webhook configuration page. |
nice work! |
The build process for Sphinx is broken since some time back. The problem originates from the fact that we don't even check it in the CI. We have a job to validate
make sphinx
however it doesn't do anything:https://github.com/nornir-automation/nornir/blob/v3.4.1/Makefile#L25
In #855 Sphinx was upgraded from version 4.5.0 to version 6.2.1 since then the builds at https://readthedocs.org/projects/nornir/builds/ have started to fail but because we didn't validate anything within the CI nobody noticed.
I'm not sure if there are any vulnerabilities in the earlier version or why it was upgraded (if there was a reason). If it doesn't have any issues with security I'd suggest to downgrade and activate the CI job just to have it tracked and then look at what's needed to upgrade. Alternatively check what is required for it to work using the current version.
Also on Read the Docs it looks like it would build for for the
stable
ordevelop
branches that doesn't exist, but not formain
. Could be that I'm just missing something as I don't have any permissions on RTD. @dbarrosop, can you perhaps have a look and see if you can activate the builds for themain
branch as well?The text was updated successfully, but these errors were encountered: