andygrove commented on issue #6062:
URL:
https://github.com/apache/datafusion-comet/issues/6062#issuecomment-5750544640
Refining the "likely cause" above, because a local reproduction turned up a
second candidate that is at least as likely, and a third layer of swallowing.
`@mermaid-js/mermaid-cli` declares `puppeteer` as a **peer** dependency and
ships `puppeteer-core`, so the browser `mmdc` drives comes from puppeteer's
`postinstall`. That script is:
```js
try {
const {downloadBrowsers} = await importInstaller();
await downloadBrowsers();
} catch (error) {
console.warn('Browser download failed', error);
}
```
It catches its own failure and exits 0. So a flaky or blocked browser fetch
during `npm install -g @mermaid-js/[email protected]` leaves a **green
install step with no browser**, and `mmdc` then dies at launch:
```
Error: Could not find chrome-headless-shell (ver. 153.0.8010.36). This can
occur if either
1. you did not perform an installation before running the script ...
```
which `sphinxcontrib-mermaid` turns into a warning and a dropped diagram.
Three layers, each one silent.
That is the exact error the reproduction produced. It does not prove it is
what happened on the runner — the browser fetch is blocked in my environment,
so I cannot separate it from the AppArmor sandbox theory, and the job log for
the docs run is not reachable from here. But it does mean there are two
plausible causes rather than one, and both are cheap to close out:
- an explicit `puppeteer browsers install chrome-headless-shell` after the
npm install, where a failure is allowed to fail the job, removes the
silent-no-browser case
- the `--no-sandbox` puppeteer config removes the AppArmor case
Whichever one it was, the render check reports the actual `mmdc` stderr, so
the next docs run says so outright instead of publishing a hole.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
