Improve exception traceability
Registered by
Joshua Harlow
It would be nice to denote the location (and possible the path?) of an exception which is emitted from a task to aid in debugging the chain of tasks that caused this task to fail. This can help in debugging the tasks that were the predecessors of the failing task and improves figuring out the root cause of the tasks exception.
Blueprint information
- Status:
- Complete
- Approver:
- None
- Priority:
- Medium
- Drafter:
- Joshua Harlow
- Direction:
- Approved
- Assignee:
- Joshua Harlow
- Definition:
- Approved
- Series goal:
- None
- Implementation:
-
Implemented
- Milestone target:
- None
- Started by
- Joshua Harlow
- Completed by
- Joshua Harlow
Related branches
Related bugs
Sprints
Whiteboard
Gerrit topic: https:/
Addressed by: https:/
Track execution cause nodes and triggered nodes
(?)
