-
Notifications
You must be signed in to change notification settings - Fork 21
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
Executable Does Not Return Error in Powershell #92
Comments
Interesting. The main method (in C#) returns 0 on success, 1 on failure. That isn't reflected in PowerShell? |
Thanks for checking this. Here is what I found, and I can reproduce it for you and link you to it in the pipeline tomorrow If the argument provided for database is invalid, it returns a long list of exceptions to the console but doesn't actually produce an error or exit code. |
Odd since even with an empty command line it gives me: delta-kusto 0.8.2 ERROR(S): -v, --verbose Set output to verbose messages. -p, --parameter Required. Set parameter file path. -o, --override Parameter path overrides (list). --help Display this help screen. [...]\delta-kusto.exe (process 19740) exited with code 1. |
Here is an instance I came across several times in my error testing. I'll share a link to the logs and also repost the logs below, in case you come up against missing ADO access:
Code Snippets:
|
I'm using this program to automate synchronization of our clusters to source control. I am finding that deltakusto.exe does not actually return an error to the console when it encounters an error.
If it logs an error, the $LASTEXITCODE of powershell is not modified nor does it return any error codes. The only way to determine if it ran successfully or not seems to be to print its output to a file and scan it for error codes.
The text was updated successfully, but these errors were encountered: