List all the exceptions that happened during heuristic execution at the end · Issue #86 · giganticode/bohr-runtime · GitHub
More Web Proxy on the site http://driver.im/
You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, if an exception occurs when a heuristic is applied to a dataset, it will be logged (with the stack trace) and BOHR will go on with the execution of other heuristics. This approach has two cons:
If the same exception occurs for every data point, logs got very polluted;
The exception might be a problem with the framework (as opposed to a bug in heuristic definition), that's why it would be good to interrupt execution, or at least to display the list of all exceptions that occurred at the end so that we could check if any exceptions were the fault of the framework
The text was updated successfully, but these errors were encountered:
Currently, if an exception occurs when a heuristic is applied to a dataset, it will be logged (with the stack trace) and BOHR will go on with the execution of other heuristics. This approach has two cons:
The text was updated successfully, but these errors were encountered: