-
Notifications
You must be signed in to change notification settings - Fork 10
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 #49
Comments
@durack1 Can you provide me with something better?
|
Similar time overlap of these 2 files. Actually the file timestamps gave a clue... The first date is
and
|
@dnadeau4 the reason this issue was generated was that when called in a script, the runtime errors (rather than stdout, stderr output) was causing problems. In most cases that I am aware of, the issue is with the input data, so there are problems, but the way that |
@durack1 you can call cdscan from inside a script cdms2.cdscan.main(["cdscan","-x","crap.xml","*.nc"]) |
@doutriaux1 that's exactly what I am doing, but the issue is that runtime failures then trip scripts over.. I was suggesting that as |
I tripped on that message It does not tell us that this is a time issue, and I did not understand why |
@durack1 this is a run time error and the program cannot continue. I could raise another kind of exception like "value error". You will still have the back trace, that is how python stops. |
@dnadeau4 the issue for me was rather than returning a |
The following problems cause runtime failures in
cdscan
rather than gracefully being caught in an error and quitting..Migrated from: CDAT/cdat#1512
The text was updated successfully, but these errors were encountered: