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: Re: Pandoc error 10 when compiling document and fetching from fonts.gstatic.com
Date: Sat, 10 Jun 2023 01:48:31 -0700 (PDT)	[thread overview]
Message-ID: <d229eff4-6162-4a3b-9604-4361230cceabn@googlegroups.com> (raw)
In-Reply-To: <CADAJKhANwvUw0HvAQwD5SuzsCys8VGPuvoAEL7rDhqmm5+7xfQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>


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

It is the output from an R system() call to pandoc, which returns the 
pandoc error code. One thing I did check was that it wasn't a 1 with a 0 
concatenated on the end through a missing \n or something silly like that. 
It does seem to be a return code from pandoc, but I will check with 
rmarkdown too. It is frustrating because I can't reliably reproduce it, 
probably because it something network-related.

On Friday, June 9, 2023 at 6:25:31 PM UTC+1 BPJ wrote:

> It seems from the cited error message like it is rmarkdown (Rmarkdown) 
> which exits with code 10, so probably not a Pandoc issue at all.
>
> Den fre 9 juni 2023 17:34John MacFarlane <fiddlo...-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> skrev:
>
>> That's rather strange because we don't emit error code 10:
>> https://pandoc.org/MANUAL.html#exit-codes
>> But it's a bit hard to diagnose these issues that involve external code. 
>> If you can reproduce the issue with pandoc by itself, that would be 
>> helpful.  Also it could be useful to know what pandoc version is being used.
>>
>>
>> > On Jun 9, 2023, at 1:41 AM, Richard Morey <richar...-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote:
>> > 
>> > I've posted this on StackOverflow here 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.
>> > 
>> > 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.
>> > 
>> > 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 - 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
>> > 
>> > 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-discus...-/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
>> .
>>
>> -- 
>> 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-discus...-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
>>
> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/pandoc-discuss/336872A1-2E6F-4BCB-801B-1230E2455ED3%40gmail.com
>> .
>>
>

-- 
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/d229eff4-6162-4a3b-9604-4361230cceabn%40googlegroups.com.

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

  parent reply	other threads:[~2023-06-10  8:48 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-09  8:41 Richard Morey
     [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 [this message]
     [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=d229eff4-6162-4a3b-9604-4361230cceabn@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).