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
Only the error message is displayed when there is an error loading a Python script. I think it would be beneficial to be able to see the full traceback. There are some situations when writing protocols where it would be highly beneficial to see the full traceback especially without access to the debugger.
expected behavior
I am proposing that the full traceback be displayed when the developer tools option is turned on.
The text was updated successfully, but these errors were encountered:
mcous
added
feature
Ticket is a feature request / PR introduces a feature
app
Affects the `app` project
api
Affects the `api` project
labels
Jul 10, 2018
Good idea, the traceback in the console / app logs would be useful in these situations. I just did some experimenting, and it's not too hard to tweak things so the API sends it over to the app in the event of an error. Gonna see if I can sneak this in tomorrow
mcous
changed the title
FEATURE REQUEST: Show full traceback when developer tools are enabled
RPC: Remote call errors should include traceback for logging in the app
Jul 10, 2018
current behavior
Only the error message is displayed when there is an error loading a Python script. I think it would be beneficial to be able to see the full traceback. There are some situations when writing protocols where it would be highly beneficial to see the full traceback especially without access to the debugger.
expected behavior
I am proposing that the full traceback be displayed when the developer tools option is turned on.
The text was updated successfully, but these errors were encountered: