Users report register gets are timing out and saturating the max number of caget attempts in newer releases (>v7.1.0). This coincides with the change in v7.2.0 over to PV caching, and is apparently due to a subtle difference in the pyepics default timeout for register gets using epics.caget (which has a default timeout of 5 sec, and is what we used to use before PV caching) versus epics.PV.get (which is what we now use, but apparently has a default timeout of 2 sec).
Describe the bug
Users report register gets are timing out and saturating the max number of
caget
attempts in newer releases (>v7.1.0). This coincides with the change in v7.2.0 over to PV caching, and is apparently due to a subtle difference in thepyepics
default timeout for register gets usingepics.caget
(which has a default timeout of 5 sec, and is what we used to use before PV caching) versusepics.PV.get
(which is what we now use, but apparently has a default timeout of 2 sec).Snippet for verifying in latest release v7.3.4;
Will fix by adding timeout as an option to the underlying pysmurf
_caget
call with 5 sec default value. E.g.