hartym
commented
5 years ago do-not-edit-start-codetree-epic-issues
Issues in this epic:
| Title | Milestone | Assignees | Stage | State |
|---|---|---|---|---|
 Handle errors using a special stream in graph. #319 |
0.8 | N/A | Open | |
| Node should be available in error queue #318 |
0.8 | N/A | Open | |
| Make the error handling queue available from outside (if not consumed) #317 |
0.8 | N/A | Open | |
| Add warning management to nodes. #221 |
N/A | N/A | Open | |
 Distinguish between Error and Fatal errors in stats #259 |
0.7 | N/A | Closed |
One critical feature to better handle pipelines is to have builtin ways to manage (especially non-fatal) errors. As our executors currently catch errors in execution, it should be pretty straightforward to have a special queue for errors (the same way there is stdout and stderr on unix systems) that can be used to let the user choose how to handle those.