The current Device class only raises errors if raise_on_error is set to true and the errors are "seen" during synchronous read/write operations. This leaves out anything that is either an Event, or unpaired Reads (e.g.: read dump). We should consider making this behavior uniform and instead raise before dispatching the messages to their own thread.
I should note, this is currently the behavior we have in the Bonsai client, where EVERY message can raise the error.
The current Device class only raises errors if
raise_on_erroris set to true and the errors are "seen" during synchronous read/write operations. This leaves out anything that is either an Event, or unpaired Reads (e.g.: read dump). We should consider making this behavior uniform and instead raise before dispatching the messages to their own thread.I should note, this is currently the behavior we have in the Bonsai client, where EVERY message can raise the error.