Command fails without error logs due to suppressed output

[hokaccha]

The following command fails without providing error logs, making debugging difficult:

Command failed: "/home/runner/work/dockan/dockan/node_modules/.bin/mmdc" -i "/tmp/prisma-erd-l9eLKO/prisma.mmd" -o "/home/runner/work/dockan/dockan/docs/erd.svg" -c "/tmp/prisma-erd-l9eLKO/config.json" -p "/tmp/prisma-erd-l9eLKO/puppeteerConfig.json"

The issue arises because the child_process.execSync function is configured with stdio: 'ignore'.

You can find the relevant code here:

prisma-erd-generator/src/generate.ts

Lines 505 to 507 in 9bfc73b

	child_process.execSync(mermaidCommand, {
	stdio: 'ignore',
	});

This configuration suppresses both stdout and stderr output. By modifying the code to allow stdio output, the following error was revealed:

Error: Failed to launch the browser process!
[0115/033116.841034:FATAL:zygote_host_impl_linux.cc(127)] No usable sandbox! Update your kernel or see https://chromium.googlesource.com/chromium/src/+/main/docs/linux/suid_sandbox_development.md for more information on developing with the SUID sandbox. If you want to live dangerously and need an immediate workaround, you can try using --no-sandbox.

This error was resolved by addressing issues related to Puppeteer and the Linux sandbox environment, as documented in the following resources:

• Puppeteer Troubleshooting Guide
• Mermaid CLI Issue #730

To improve the developer experience, it is recommended that prisma-erd-generator outputs error logs instead of suppressing them, facilitating easier debugging of similar issues in the future.

[keonik]

On it!