New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Provide clear error message on missing xsltproc dependency #6674
Comments
This looks like it's almost done so I'm leaving it for 3.13.0 since we have other parallel things going on still anyway. It shouldn't block at 3.13.0 release though, so I'll bump it to 3.14.0 later if it comes to it. |
I have moved to AT but forgot to confirm that is ready: PR #7301 , branch Test steps
Another use case is instead of remove or rename the command just change the permissions access to not allow the API to execute it ( |
@mrsarm , the
Basically the code in the
and the output for this:
Did you wanna have a look and see why this is? Thanks. |
LG atm. Must have to do with the operating system, as it seems to behave differently on mac than on Linux.
Please feel free to merge @mrsarm . |
Reopening the issue because the workaround only solved the problem for Node v10 and v12. Node v8 and v14+ requires other 2 approaches that I'm addressing in #7335 |
@ngaruko can you work this secondary fix. I don't have the multiple operating systems you've defined. |
@newtewt I think it was not an OS issue but a node version issue. With node 8, the api crash but there the human readable error does not show. With node 14, I was able to see the error with code EPIPE thrown. |
I have verified that it works on all supported versions of node (v8 to v14). To help test with ease, I stripped the Feel free to merge @mrsarm |
Nice trick @ngaruko 👏 Thanks ! |
API fails with a cryptic error when xsltproc is missing
I believe we should explicitly mention that in the error
Related to #6455
This was experienced in 3.10
The text was updated successfully, but these errors were encountered: