From: Shakrmaker <tojonmz-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: pandoc-discuss <pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
Subject: GitHub Actions - openBinaryFile: does not exist (No such file or directory)
Date: Mon, 28 Jun 2021 10:03:13 -0700 (PDT) [thread overview]
Message-ID: <06a85c25-bad6-4c22-a184-a3becb9f64dbn@googlegroups.com> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1816 bytes --]
Hi Everyone,
Apologies, but I've searched all the threads here (StackOverflow, etc), and
while I've found lots of folks hitting it, I haven't found my solution. I
set up a GitHub Action in my repo on push, essentially using the provided
example on https://github.com/pandoc/pandoc-action-example.
I can run and access my input files fine with a simple run ls, via an
/absolute/path, via ${{ github.workspace }}/path, or via
$GITHUB_WORKSPACE/path so I know they are there.
But when I try to call pandoc with the yaml, I get the classic error:
pandoc: *(my-valid/path*): openBinaryFile: does not exist (No such file or
directory)
My yaml:
on: push
jobs:
convert_via_pandoc:
runs-on: ubuntu-18.04
steps:
# Checks-out repository under $GITHUB_WORKSPACE, so job can access it
- uses: actions/checkout@v2
- run: ls [valid/path].md
- uses: docker://pandoc/core:2.11.2
with:
args: >- # break args into multiple lines
-s
-M title="My Title"
-o output.html
-f markdown
[valid/path].md
Here's an example showing the path is valid, and the failure when I try to
access that path as the input file (same occurs using $GITHUB_WORKSPACE,
etc).
I am a newbie to both GitHub Actions and Pandoc, so it must be something
obvious to the experts here. What am I doing wrong?
Thanks in advance.
--
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/06a85c25-bad6-4c22-a184-a3becb9f64dbn%40googlegroups.com.
[-- Attachment #1.2: Type: text/html, Size: 2995 bytes --]
[-- Attachment #2: run2_failure.jpg --]
[-- Type: image/jpeg, Size: 381871 bytes --]
next reply other threads:[~2021-06-28 17:03 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-28 17:03 Shakrmaker [this message]
[not found] ` <06a85c25-bad6-4c22-a184-a3becb9f64dbn-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2021-06-28 17:29 ` John MacFarlane
[not found] ` <m28s2tnbi3.fsf-jF64zX8BO0+FqBokazbCQ6OPv3vYUT2dxr7GGTnW70NeoWH0uzbU5w@public.gmane.org>
2021-06-28 21:28 ` Shakrmaker
[not found] ` <b9b67058-9a97-471a-b6d6-0021ea504a36n-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2021-06-28 21:39 ` Shakrmaker
[not found] ` <07d841b9-a12f-450d-92c3-60d519876708n-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2021-06-28 22:06 ` Shakrmaker
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=06a85c25-bad6-4c22-a184-a3becb9f64dbn@googlegroups.com \
--to=tojonmz-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).