-
Notifications
You must be signed in to change notification settings - Fork 346
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
Lots of warnings now building the docs #7253
Comments
I get those too and found that someone else had apparently the same problem. Maybe it is a lead worth following? |
We put faith in @seisman or @maxrjones to figure this out at some point. |
Hmm, I only get these (and half come from non-committed branches
|
Now I also get hundreds of them. |
Sphinx makes all explicit targets available globally, thus all targets must be unique in the entire documentation. In our docs, we define targets like As far as I know, there is no option to suppress these warnings. So our only choice is to redirect all these warnings into a log file, and then use |
I agree, silly decision by Sphinx. The grepped log is a good suggestion |
I can't understand that no one has posted a feature request regarding this with the sphinx folks. appending |
There are already some complaints similar to our situation (e.g., sphinx-doc/sphinx#10202).
I don't think it will work. The same target is still defined multiple times in the entire docs. |
After filtering out the useless "duplicate label" warnings, here are the useful warnings, and some are critical:
|
Maybe this is standard but recently switched to home-brew and after git pull etc and building docs I get an enormous list of warnings like this:
Anything obvious to those who speak RST?
The text was updated successfully, but these errors were encountered: