You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The builder currently doesn't access to the saved environment, so it can only see pages that are new or have changed since the last build, possibly leading to an incomplete sitemap.
Work around
To get around this you can manually clean the build directory or use the -E flag to not use the saved environment and rebuild completely as part of your deployment process.
Possible fix
The saved environment is pickled after the parsing stage, so accessing it may make it possible to always produce a full sitemap. Using doctree-resolved instead might be a possibility.
Temp fix
Test if sphinx is running a partial build and output a warning.
The text was updated successfully, but these errors were encountered:
Let me explain the context: We use Sphinx for a LaTeX FAQ that contains more than 1200 pages. We've worked hard to ensure that only modified pages are automatically (thanks to a GitLab CI/CD process) (re)generated each time a contributor modifies a source file (Markdown). In fact, recompiling all the pages each time was too time-consuming (around 15 minutes) and unnecessarily energy-consuming.
So, when a contributor modifies a single source file, only the corresponding .html file is (re)generated) and we are very happy with this, so the workaround you suggest cannot be an option for us); but, now, the problem is, the sitemap.xml contains (almost?) only the path to the corresponding .html file.
We'd be delighted if you could provide with a fix! 😃
Issue
The builder currently doesn't access to the saved environment, so it can only see pages that are new or have changed since the last build, possibly leading to an incomplete sitemap.
Work around
To get around this you can manually clean the build directory or use the -E flag to not use the saved environment and rebuild completely as part of your deployment process.
Possible fix
The saved environment is pickled after the parsing stage, so accessing it may make it possible to always produce a full sitemap. Using doctree-resolved instead might be a possibility.
Temp fix
Test if sphinx is running a partial build and output a warning.
The text was updated successfully, but these errors were encountered: