Open SanshiroEnomoto opened 11 months ago
@SanshiroEnomoto do you have a suggested solution?
This could also get caught up in better error handling that Christine mentioned on today's call - so it may be part of a broader problem/solution
As Walter said, I think this is an issue related to error reporting. Crashing is fine, as keeping going would not produce useful data anyway (stopping would be better, though), but it was very difficult for me (who is not familiar with the code set) to figure out this simple cause. The worst thing is the message of Caught unhandled exception. what(): Exception: name 'ThrowReply' is not defined
, which I consider is a bug and needs to be fixed.
I believe the unhandled exception in this issue will be fixed by one of the deficiencies listed in https://github.com/driplineorg/dripline-cpp/issues/103.
I've also made a dedicated issue for exception handling in dl-py itself: #166. I have not yet looked through the code in Implementations to consider its exceptions use.
For a SCPI device that accepts
READ?
for readout, if I putREAD?
in thebase_str
(which is wrong; should beREAD
), Dripline crashes instead of printing an error message: