Update - this was caused by https://github.com/jgm/pandoc/issues/8779 (the 10 is "bus error: 10"), and solved by installing the (non-homebrew) release of pandoc.

On Tuesday, June 13, 2023 at 9:06:18 PM UTC+1 Richard Morey wrote:
Thanks, everyone, for your help. I've finally managed a (nearly) 100% reproducible version that shows the mysterious "pandoc error 10" with minimal code and posted an issue at rstudio/rmarkdown: https://github.com/rstudio/rmarkdown/issues/2495

Best,
Richard

On Saturday, June 10, 2023 at 4:15:37 PM UTC+1 John MacFarlane wrote:
I've searched the code base and there's nowhere we return a 10 error code...

> On Jun 10, 2023, at 1:48 AM, Richard Morey <richar...-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote:
>
> 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...-/JYPxA39Uh5TLH3MbocFFw@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...-/JYPxA39Uh5TLH3MbocFFw@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-discus...-/JYPxA39Uh5TLH3MbocFFw@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.

--
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-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org.
To view this discussion on the web visit https://groups.google.com/d/msgid/pandoc-discuss/7d99685a-9f0c-419e-905f-6455dcc4a4ffn%40googlegroups.com.