public inbox archive for pandoc-discuss@googlegroups.com
 help / color / mirror / Atom feed
From: Richard Morey <richarddmorey-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: pandoc-discuss <pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
Subject: Pandoc error 10 when compiling document and fetching from fonts.gstatic.com
Date: Fri, 9 Jun 2023 01:41:24 -0700 (PDT)	[thread overview]
Message-ID: <ec43be1c-e46d-4323-a70e-c97a90e670f0n@googlegroups.com> (raw)


[-- Attachment #1.1: Type: text/plain, Size: 3356 bytes --]

I've posted this on StackOverflow here 
<https://stackoverflow.com/questions/76422082/pandoc-error-10-when-compiling-document-and-fetching-from-fonts-gstatic-com> 
but have not gotten any interest in several days, so I'm posting here.

I'm having trouble consistently compiling a particular document with 
rmarkdown::render. I cannot reproduce the issue reliably, unfortunately (it 
happens roughly 1/3 of the time; consostent with it being a network error, 
maybe?), but when it fails, I get the error: 

pandoc document conversion failed with error 10 

from rmarkdown. The "10" is the return code from the system command that 
runs pandoc here 
<https://github.com/rstudio/rmarkdown/blob/10863429024e236389a48f40ab1485620d53d311/R/pandoc.R#L107>
.

When I set pandoc to give debugging information with --verbose the 
following lines are the last ones in stderr:
[INFO] Fetching 
https://fonts.gstatic.com/s/opensans/v34/memvYaGs126MiZpBA-UvWbX2vVnXBbObj2OVTSKmu1aB.woff2... 

[INFO] Fetching 
https://fonts.gstatic.com/s/opensans/v34/memvYaGs126MiZpBA-UvWbX2vVnXBbObj2OVTSumu1aB.woff2... 

[INFO] Fetching 
https://fonts.gstatic.com/s/opensans/v34/memvYaGs126MiZpBA-UvWbX2vVnXBbObj2OVTSOmu1aB.woff2... 

[INFO] Fetching 
https://fonts.gstatic.com/s/opensans/v34/memvYaGs126MiZpBA-UvWbX2vVnXBbObj2OVTSymu1aB.woff2... 

[INFO] Fetching 
https://fonts.gstatic.com/s/opensans/v34/memvYaGs126MiZpBA-UvWbX2vVnXBbObj2OVTS2mu1aB.woff2... 

[INFO] Fetching 
https://fonts.gstatic.com/s/opensans/v34/memvYaGs126MiZpBA-UvWbX2vVnXBbObj2OVTSCmu1aB.woff2... 

[INFO] Fetching 
https://fonts.gstatic.com/s/opensans/v34/memvYaGs126MiZpBA-UvWbX2vVnXBbObj2OVTSGmu1aB.woff2... 

Error : pandoc document conversion failed with error 10 

The last line varies, but it always seems to be one of these fonts that is 
the last thing pandoc reports before the error (there are 24 of these font 
fetches in this particular document, as shown by the output in a successful 
compile).

This leads me to believe that there is a problem in fetching one of these 
fonts, but there's no output that says what the problem actually *is*, and 
Error 10 does not seem to be a valid error code from pandoc: pandoc error 
codes 
<https://github.com/jgm/pandoc/blob/c9825761338f56209f69782da0087f9e27fa577b/src/Text/Pandoc/Error.hs#L154>
.

I'm sort of stuck debugging until I figure this out.

I also note there is a similar issue here: NYTimes and 538 Themes Give 
Pandoc Error 10 <https://github.com/jthomasmock/gtExtras/issues/89> - as a 
bonus, it even seems to be related to fonts.gstatic.com, but that out seems 
to be more specific, including a [WARNING] that I don't see in mine.

In case they are helpful, I've put the logs of a failure and success and 
the pandoc command that was run in a gist here: logs 
<https://gist.github.com/richarddmorey/c88bdc16ddc37ac5ff4f34b68cfcdd70>

I'd appreciate any insights into what could cause this and how to fix it.

Best,
Richard

-- 
You received this message because you are subscribed to the Google Groups "pandoc-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to pandoc-discuss+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
To view this discussion on the web visit https://groups.google.com/d/msgid/pandoc-discuss/ec43be1c-e46d-4323-a70e-c97a90e670f0n%40googlegroups.com.

[-- Attachment #1.2: Type: text/html, Size: 4913 bytes --]

             reply	other threads:[~2023-06-09  8:41 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-09  8:41 Richard Morey [this message]
     [not found] ` <ec43be1c-e46d-4323-a70e-c97a90e670f0n-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2023-06-09  9:19   ` Richard Morey
2023-06-09 15:33   ` John MacFarlane
     [not found]     ` <336872A1-2E6F-4BCB-801B-1230E2455ED3-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2023-06-09 15:34       ` John MacFarlane
     [not found]         ` <1E0EA465-B672-4B97-87A1-A49D4CC9F568-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2023-06-09 15:41           ` John MacFarlane
2023-06-09 17:25       ` BPJ
     [not found]         ` <CADAJKhANwvUw0HvAQwD5SuzsCys8VGPuvoAEL7rDhqmm5+7xfQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2023-06-10  8:48           ` Richard Morey
     [not found]             ` <d229eff4-6162-4a3b-9604-4361230cceabn-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2023-06-10 15:15               ` John MacFarlane
     [not found]                 ` <DA9E594B-6FAB-4D65-BA2E-814EFCC889F7-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2023-06-13 20:06                   ` Richard Morey
     [not found]                     ` <b009e279-b9b5-48bb-b44f-3f86686b91een-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2023-06-14 10:50                       ` Richard Morey

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=ec43be1c-e46d-4323-a70e-c97a90e670f0n@googlegroups.com \
    --to=richarddmorey-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
    --cc=pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).