Closed aaronparker closed 1 year ago
You can see in the logs that the exit code is 0
so your pipeline should not fail just because something was written to stderr
(some puppeteer deprecation warning in this case). I would guess this is most likely a problem with your pipeline configuration.
Looking at this question on SO: https://stackoverflow.com/questions/58621159/azure-command-line-task-what-is-the-difference-between-fail-on-standard-error
Most likely you have ticked this "fail on standard error" checkbox in your task.
🤦♂️ Ah, of course! Thank-you
Context:
Describe the bug:
Running md-to-pdf on an Azure Pipeline with the following command results in the error in the debug log below:
The pipeline with no modifications has been running OK up until about a week ago. The same command run locally on macOS with Node.js 20.0.0 runs OK. I'm not 100% certain this is actually an md-to-pdf issue - I have tested with md-to-pdf 5.2.3, 5.2.2. and 5.2.1.
I will try with the Pipeline configured to not fail on this step and see whether the HTML is still produced.