-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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
Pandoc failure when building in GitHub CI #1960
Comments
Hi @max-heller, before I start looking more into this, do you recognize this error off the top of your head? 🙂 Cc @henrif75 and @djmitche who looked at other PDF errors in #1911. |
These have to do with Pandoc attempting to embed remote images in the PDF.
This error relates to this workaround
I'm not sure about this one and can't reproduce it locally. I don't see any images with |
Thanks @max-heller for the explanation! Your analysis seems spot on: the error went away on the third run of the build. It would be nice if we could make our build resilient to this somehow... Perhaps I should just remove the shields.io images from the source when generating the book. I don't think they fit very well into a PDF 🙂 |
Agreed, although I'm not sure of a good general solution. Maybe |
Yeah, for this particular case that would work well. But it seems like the wrong place to add this kind of logic — I feel it should be the caller of I think we can close this issue for now: it's a transient error and now we know that it should go away after a while. If it pops up again, then we can take another loop at implementing some kind of retries (or more likely: strip out the unreliable images). |
In #1951, the PDF generation failed with:
It is the same error message in the run for German, Danish.
For Bengali, the error instead says
Note that it's a
.yml
file here, but.vs
files above.The text was updated successfully, but these errors were encountered: