Async functionality should propagate the errors/exceptions to the caller

epics-base / pvaPy

pvaPy provides Python bindings for EPICS pvAccess

https://epics.anl.gov/extensions/pvaPy/production/index.html

Other

36 stars 22 forks source link

Async functionality should propagate the errors/exceptions to the caller #68

Closed MaticPogacnik closed 3 years ago

MaticPogacnik commented 3 years ago

Recently the asyncGet was added, which works as expected. But the exceptions (e.g. Timeout) are just logged and not propagated to the user.

I see two possibilities how this could be added (there are probably more):

Add a separate callback, which is called on the error.
Add extra arguments to the existing callback, which provide the status information.

@sveseli

anjohnson commented 3 years ago

Hi Matic, FYI Sinisa is now "out of the office" until mid-September, so you might not get a response until he gets back (although it wouldn't surprise me if he checks his email occasionally).

echandler-anl commented 3 years ago

FYI we found a separate issue related to async: async get/put block if they can't connect to the PV. Connection needs to happen on the async thread.

sveseli commented 3 years ago

@MaticPogacnik fixes have been incorporated into the code as of release 4.0.1.