-
Notifications
You must be signed in to change notification settings - Fork 68
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
Catch cdscan errors without triggering runtime failures #1512
Comments
i'll take a look but it is most likely going to be bumped to 3.0 |
It's just a matter of adding this to the trapped errors.. Could be done pretty quickly I think.. Maybe @painter1 could also take a look? |
@painter1 any cycles for this? I'll keep it as 2.4 as long as possible. |
@durack1 it does "raise" so it should exit with an error, what do you mean by "gracefully being caught in an error and exit". That's pretty much what happens here. |
I'll take another look at how I am calling this (and collecting stdout and stderr) as long as these are being sent to the correct output I should be able to fix this.. I'll report back on progress.. A question to raise is whether in the case describe above |
The following problems cause runtime failures in
cdscan
rather than gracefully being caught in an error and quitting..The text was updated successfully, but these errors were encountered: