Skip to content
This repository was archived by the owner on Jun 1, 2022. It is now read-only.

Engine: Print Debug Traceback on Graph Interpretation Error #33

Open
joeltio opened this issue Feb 5, 2021 · 1 comment
Open

Engine: Print Debug Traceback on Graph Interpretation Error #33

joeltio opened this issue Feb 5, 2021 · 1 comment
Assignees
Labels
engine Area: Engine ux User Experience

Comments

@joeltio
Copy link
Collaborator

joeltio commented Feb 5, 2021

The evaluation of the computation graph on the engine is done through a recursive function. The function does not have sufficient error handling to pinpoint the exact node which caused the error. This makes debugging graphs difficult.

Currently, the only way to debug the graphs is through a debugger, stepping through each node manually.

@joeltio joeltio added the engine Area: Engine label Feb 5, 2021
@mrzzy mrzzy added the ux User Experience label Feb 7, 2021
@joeltio joeltio self-assigned this Feb 10, 2021
@joeltio
Copy link
Collaborator Author

joeltio commented Feb 13, 2021

C++11 has introduced nested exceptions, allowing us to create our own traceback. This is likely what will be used to implement this. See https://en.cppreference.com/w/cpp/error/nested_exception

@mrzzy mrzzy changed the title Engine cannot determine which node throws exception Engine: Print Debug Traceback on Graph Interpretation Error Feb 14, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
engine Area: Engine ux User Experience
Projects
None yet
Development

No branches or pull requests

2 participants