I’m trying to code a generic type of error handler that I can call from the except clauses from different scripts where the error_handler procedure can take different routes depending on what is passed to it. Ideally, I want a generic error handler that will catch any/all types of errors. My quest…

We have tons of error handling where the except clauses look like (see image below) from a UDT Tag Value Change script. I want to replace this code (code that builds parameters, calls Named Query and logs to the database) I want to replace it with a single line code like error_handler() (see my or…

getattr(e, 'message', repr(e)) is retrieving the property named message from e, and if e does not have a message property, it’s returning repr(e). repr can be distinct from str, but usually won’t be for Java objects, including exceptions. It’s not clear from your snippet if Exception is Python’s bui…

I no longer use from java.lang import Exception. I use from java.lang import Throwable instead. Python’s Exception will not catch java exceptions at all. Java’s Throwable will not catch any python exceptions. You must have two separate except clauses everywhere. See also the PythonAsJavaExcepti…

What about import traceback traceback.format_exc() Phil? Does this miss something?

It doesn’t play nice with the logging system. For loggers to deliver a neat traceback, you have to supply a subclass of java’s Throwable.

Thank you, yes, the (message) property of the e object. You mentioned that (if e does not have a message property). What types of errors or when would e not have the message property? My snippet is from an Ignition UDT script. There are not any (from java.lang import Exception) lines, or anything …

Can you give an example of what that would look like (two except clauses). I want to catch errors on system.tag.write, and try: / except: is not catching the error. The vision client user does not have writePermissions for the first tag in this list, so I want the whole routine to end. I'm print…

That's because a write that fails is not an error per se. You need to store the return from each write and check if the value is good or not

As Nick said, a failed write doesn't raise an exception, so there's nothing to catch. I use this to check for failed writes: base_logger = system.util.getLogger("Utils").createSubLogger("Tags") def write(paths, values, logger=None): if logger is None: logger = base_logger write_return = syste…

Inductive Automation Forum

Generic Python error handler?

Ignition

ignition81, scripting

zacht June 9, 2022, 9:10pm 2

Import not Work Ignition

Jython’s Exception class does not inherit from Java’s base exception class - so exceptions thrown in Java code (ie, everything written by Inductive Automation) are not caught by Exception clauses. You have to catch both possible exceptions: import java.lang.Exception try: # something something something except Exception, e: # jython exception except java.lang.Exception, e: or import java.lang.Exception try: # something something something except (Exception, java.lang.Exception),…

show post in topic

Home
Categories
Guidelines
Terms of Service
Privacy Policy

Powered by Discourse, best viewed with JavaScript enabled