Open durack1 opened 9 years ago
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 cdscan
should try to generate output as it does with overlapping times in multiple files etc.. This case errors, whereas other similar cases throw a warning instead.. The consistency of this error vs warning is probably a better issue to pose..
The following problems cause runtime failures in
cdscan
rather than gracefully being caught in an error and quitting..