Task #11147 (new)
Opened 11 years ago
Last modified 9 years ago
RFE: Error handling in scripts
| Reported by: | jamoore | Owned by: | |
|---|---|---|---|
| Priority: | critical | Milestone: | Asynchronous |
| Component: | Scripting | Version: | 4.4.8 |
| Keywords: | n.a. | Cc: | wmoore, pwalczysko |
| Resources: | n.a. | Referenced By: | n.a. |
| References: | n.a. | Remaining Time: | n.a. |
| Sprint: | n.a. |
Description (last modified by jamoore)
See rather long discussion on ome/scripts#31.
We should standardize how error states propagate from scripts up into the clients. What counts as a terminal failure (red X)? What is just a warning? For example, if only one of several images cannot be handled, is that a warning? What if only one image is passed?
There are several mechanisms for the scripts themselves to signal error state without resorting to message parsing which we can make use of.
Change History (2)
comment:1 Changed 11 years ago by jamoore
- Description modified (diff)
- Version set to 4.4.8
comment:2 Changed 9 years ago by jamoore
- Milestone changed from 5.x to Asynchronous
Note: See
TracTickets for help on using
tickets.
You may also have a look at Agilo extensions to the ticket.
