How to display a nice Error stack when receiving an error event?

Dear PyTango experts and users,

I'm still a newbee in PyTango, so sorry if I missed something obvious. smile
I was trying to execute an old piece of code I found in some old training slides and I was trying to update the code to make it work with latest pytango and with python3.
I have been using latest itango conda package to try out the code.

I encountered a problem when trying to use the tango.Except.print_error_stack method with the errors received from an EventData object as parameter.

Here is the code:
import tango
import time
dev = DeviceProxy("sys/tg_test/1")
while (i < 60):
if not dev.is_event_queue_empty(eve_id):
print("Event from device",event_data.device.dev_name())
print("for attribute",event_data.attr_name)
if event_data.err:
print("Error sent with event:")
if event_data.attr_value.quality == tango.AttrQuality.ATTR_INVALID:
print ("Attribute data is invalid")
print("Attribute value =", event_data.attr_value.value)

If I stop the TangoTest device server to generate an error event, here is what is displayed:

Event from device sys/tg_test/1
for attribute tango://
Error sent with event:
ArgumentError: Python argument types in
did not match C++ signature:
(For more detailed information type: python_error)

It looks like tango.DevErrorList type does not exist in pytango so we cannot really use tango.Except.print_error_stack method.
Is there any alternative method to display nicely the errors received in an event?
Rosenberg's Law: Software is easy to make, except when you want it to do something new.
Corollary: The only software that's worth making is software that does something new.
Hi Reynald

Yes, I see the tango.DevErrorList type isn't exposed in Python. I don't see an easy way to use tango.Except.print_error_stack(). I didn't even know it existed!

The standard string representation of the error objects will give you a nice way to see the errors:

def handler(event):
if event.err:
for error in event.errors:
print("event OK!")

Example of usage and error. Here the device isn't configured correctly, so we get errors (using stateless=True to keep getting errors via the event system).

>>> eid = dp.subscribe_event("double_scalar", tango.EventType.CHANGE_EVENT, handler, stateless=True)

desc = The polling (necessary to send events) for the attribute double_scalar is not started
origin = DServer::event_subscription
reason = API_AttributePollingNotStarted
severity = ERR]

desc = Failed to execute command_inout on device dserver/tangotest/test, command ZmqEventSubscriptionChange
origin = Connection::command_inout()
reason = API_CommandFailed
severity = ERR]

desc = Device server send exception while trying to register event
origin = EventConsumer::connect_event()
reason = API_DSFailedRegisteringEvent
severity = ERR]

If you are just doing simple testing, there is a built-in class that handles all types of events nicely. It just prints out the first error message in the list:

>>> handler = tango.utils.EventCallback()
>>> eid = dp.subscribe_event("double_scalar", tango.EventType.CHANGE_EVENT, handler, stateless=True)
2021-10-26 13:00:37.968679 SYS/TG_TEST/1 DOUBLE_SCALAR CHANGE [API_AttributePollingNotStarted] The polling (necessary to send events) for the attribute double_scalar is not started

Register or login to create to post a reply.