gather more info when Ctrl c is not handled properly
@felix @valentin.valls @denolf @debionne
An issue to gather the different problems observed with the ctrl-c and discuss what could be done to improve the debugging of the different cases.
Case 1: Ctrl-c exits the bliss session
Case 2: Ctrl-c does not stop the scan / motors
#3859 #3656 (closed) #4187 (closed)
Case 3: Bad state/recovery after a ctrl c
None
other linked issues:
Propositions:
case 1)
-
add
try/except KeyboardInterrupt
at the highest level of the application to catch cases where the error is not caught as expected (and log the trace) -
When handling CtrlC=>SIGINT, raise a custom exception like
BlissKeyboardInterrupt(GreenletExit)
instead of justKeyboardInterrupt
to eventually distinguish Bliss mechanisms from None-Bliss mechanisms.
Edited by Valentin Valls