Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Move back to CircleCI(?)
See original GitHub issue@choldgraf I’ve just realised an issue here: so with the circleci the documentation was running with the flags: https://github.com/executablebooks/MyST-Parser/blob/ba5c56c391ced762d617c254e93db5e2c808cb1d/docs/Makefile#L23-L24
which means that it runs in “nitpick” mode -n, fails on warnings -W, but still tries to continue building the documentation even if there is a failure --keep-going.
This ensures that the CI fails on warnings, like missing references, but if won’t stop at the first warning, so that you can see all the warnings in one run and also view the final documentation.
With this new CI, it currently won’t fail on warnings.
You can add https://docs.readthedocs.io/en/latest/config-file/v2.html#sphinx-fail-on-warning, which I guess is equivalent to -nW, but there appears to be no option for --keep-going, and thus makes it tedious to not be able to identify all warnings in one run.
_Originally posted by @chrisjsewell in https://github.com/executablebooks/MyST-Parser/pull/175#issuecomment-650079264_
Issue Analytics
- State:
- Created 3 years ago
- Comments:9 (9 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
that wasn’t the issue for me: see https://github.com/readthedocs/readthedocs.org/issues/7240#issuecomment-650374579
makes sense - I’m happy with keeping this on GHA if that doesn’t pan out on RTD