Endpoint exception handling needs to be expanded

project8 / dripline

Slow controls for medium scale physics experiments based on AMQP centralized messaging

http://www.project8.org/dripline

1 stars 0 forks source link

Endpoint exception handling needs to be expanded #43

Closed laroque closed 9 years ago

laroque commented 9 years ago

Currently, if you send an invalid "set" to an endpoint, an exception is raised in the start_node program which then exits. This is clearly not a 'production' quality behavior.

The solution is better/expanded exception handling. In many cases we can probably catch the exception, pass it back as the "result" with the status modified as needed, then pass/resume.

laroque commented 9 years ago

There have been lots of try/except blocks added. I'm not sure what exactly this was supposed to be about and it seems better so I'm closing it. If someone notices this behavior, please post specific instructions for duplicating your instructions and either re-open or post a new issue.