You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Uncaught Error: Exited with code: 1
at CommandChild.pipedStdoutBuffer (file:///Users/krzkaczor/Workspace/spark/spark-alm-planner/node_modules/.pnpm/[email protected]/node_modules/dax-sh/esm/mod.js:8625:19)
(often even stack trace is not helpful).
I think the default behaviour should be to throw an error with command name that was executed and at least few final lines of stderr and stdout.
For reference, this is what bun/shell will do (output and error code both parts of the responses):
The text was updated successfully, but these errors were encountered:
Yeah it's definitely related to those tickets, I decided to create another ticket because I think this behaviour should be a default. Feel free to close this if you think the other tickets are enough.
I came up with the following to work around this. It works decently well, although you lose out on the text, json, etc. helpers on CommandBuilder since they essentially spawn internally. Would be nice if this was somehow built in to dax.
Simple code such:
Throws totally unhelpful error message like
(often even stack trace is not helpful).
I think the default behaviour should be to throw an error with command name that was executed and at least few final lines of stderr and stdout.
For reference, this is what bun/shell will do (output and error code both parts of the responses):
The text was updated successfully, but these errors were encountered: