Stuck on an issue?
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.
Documentation build hangs indefinitely for pdfhtml on master
See original GitHub issueDescribe the bug
In #1283 we re-worked the documentation structure a bit. This seems to have introduced a bug where the singlepage PDF build via HTML now hangs indefinitely.
To Reproduce
Build the book PDF via HTML with
tox -e docs-pdfhtml-update
this should hang indefinitely
Issue Analytics
- State:
- Created 2 years ago
- Comments:20 (20 by maintainers)
Top Results From Across the Web
HTML docs builds are hanging when PDF build fails #416
As of today, the builds for the HTML version of Complexity are hanging, even though the HTML version of the Complexity docs seems...
Read more >Indexer Hangs Indefinitely Causing New Documents To Fail ...
The Repository Manager applet shows that the indexer is hanging. The number of indexed documents remains the same. Restarting WebCenter Content ...
Read more >iText Knowledge Base
... pdfHTML hangs indefinitely when a specific baseURI is set ... .com/itext/i5js-sandbox/master/resources/pdfs/primes.pdf document.
Read more >Build hangs at "Collecting TOC and Index Data"
I am trying to build a PDF output that will ultimately be very large (4000 + pages). Every time I build, the process...
Read more >Natron Documentation - Read the Docs
Natron Documentation, Release 3.0.0. Common Workarounds. Luckily, there are workarounds for most Natron crashes or hangs.
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
No the key thing here is that you only need to register a node if they will actually reach the builder. Since tableofcontents nodes are all now replaced/removed in a transform (that is always applied, as opposed to the current post-transform that is not), they can never reach the builder. Hence they are not registered anywhere
@chrisjsewell @choldgraf I heard from Takeshi (on the dev community channel) and we may be able to have a look at adjusting this upstream in
sphinx.