confusing NotImplementedError in chained exception traceback
seen on ID26:
2022-04-02 14:49:21,711 optics exceptions ERROR : Traceback (most recent call last):
File "/users/blissadm/local/bliss.git/bliss/common/axis.py", line 75, in _start_one_controller_motions
controller.start_all(*motions)
File "/users/blissadm/local/bliss.git/bliss/controllers/motor.py", line 428, in start_all
raise NotImplementedError
NotImplementedError
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "src/gevent/greenlet.py", line 906, in gevent._gevent_cgreenlet.Greenlet.run
File "/users/blissadm/local/bliss.git/bliss/common/axis.py", line 78, in _start_one_controller_motions
controller.start_one(motion)
[...]
In case start_all
is not implemented, start_one
is called for each axis on the controller,
so far so good.
If start_one
fails, the exception traceback is confusing: it shows NotImplementedError
, as
exceptions are "chained".