Open gjover opened 3 years ago
I confirmed this together with @gjover . For the moment, only reproduced with an electrometer DS connected to switched-off hardware.
At a first glance, it looks like the problem has to do with the initialization of polling/events in tango attributes
It would be nice to try reproducing it with a pure software DS simulating the timeouts.
Taurus form get's stuck on the first model when this model is an attribute in timeout error.
This problem occurred reading an attribute from an electrometer DS which hardware was disconnected.
Let's be (
a/b/c/timeout_attr
) and (a/b/c/normal
) two attributes, the first producing timeout errors.The taurus form gets stuck on the first model and don't show the taurus form
taurus form a/b/c/timeout_attr a/b/c/normal
However, swapping the models, the taurus form shows up, with the second attribute in grey
taurus form a/b/c/normal a/b/c/timeout_attr
If the first model is an eval, taurus form keeps getting stuck on the timeout attribute
taurus form eval:1 a/b/c/timeout_attr
It seams to be related with the polling subscription. The error is: