I started running into an issue while using this action that seems to be linked to the markdown-to-pdf container. Haven't really changed anything on my end other than some content in markdown and some more pictures to render. Here's the error out put:
Error: Invalid protocol: data:
at Request.init (/node_modules/request/request.js:458:31)
at new Request (/node_modules/request/request.js:127:8)
at request (/node_modules/request/index.js:53:10)
at /node_modules/request/index.js:61:12
at Function.get (/node_modules/request/index.js:100:12)
at /markdown-to-pdf.js:170:11
at new Promise (<anonymous>)
at encodeImage (/markdown-to-pdf.js:169:9)
at ConvertImageRoutes (/markdown-to-pdf.js:111:22)
at processTicksAndRejections (internal/process/task_queues.js:97:5)
ERROR: SyntaxError: Invalid regular expression: /data:image/png;base64,iVBORw0KGgo....
........
omitted for brevity
........YII=/: Nothing to repeat
at new RegExp (<anonymous>)
at ConvertImageRoutes (/markdown-to-pdf.js:112:32)
at processTicksAndRejections (internal/process/task_queues.js:97:5)
at async /markdown-to-pdf.js:229:15**
Built HTML file: UserGuide.html
Built PDF file: UserGuide.pdf
Gracefully shut down image server.
(node:1) UnhandledPromiseRejectionWarning: TimeoutError: Navigation Timeout Exceeded: 30000ms exceeded
at /node_modules/puppeteer/lib/LifecycleWatcher.js:142:21
-- ASYNC --
at Frame.<anonymous> (/node_modules/puppeteer/lib/helper.js:110:27)
at Page.goto (/node_modules/puppeteer/lib/Page.js:629:49)
at Page.<anonymous> (/node_modules/puppeteer/lib/helper.js:111:23)
at /markdown-to-pdf.js:159:14
at processTicksAndRejections (internal/process/task_queues.js:97:5)
(node:1) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 1)
I did upgrade my action to use 1.0.1 in case that was the issue but I'm still getting this consistently now.