Skip to content

Show full stacktrace on eval error#130

Merged
avli merged 1 commit intoavli:masterfrom
alek-sys:master
Mar 8, 2019
Merged

Show full stacktrace on eval error#130
avli merged 1 commit intoavli:masterfrom
alek-sys:master

Conversation

@alek-sys
Copy link
Copy Markdown
Contributor

@alek-sys alek-sys commented Mar 8, 2019

Currently only first part of stacktrace is displayed, which is usually
something like 'Syntax error reading source at' without displaying root
cause. Nested stacktraces (for re-thrown exceptions) contain critical
information so they should be displayed as well.

Apparently there is a service 'stacktrace' object with a single field
called 'status' and value [done]. This needs to be filtered as it has
no data to display.

Currently only first part of stacktrace is displayed, which is usually
something like 'Syntax error reading source at' without displaying root
cause. Nested stacktraces (for re-thrown exceptions) contain critical
information so they should be displayed as well.

Apparently there is a service 'stacktrace' object with a single field
called 'status' and value [done]. This needs to be filtered as it has
no data to display.
@avli avli merged commit d6ef1b9 into avli:master Mar 8, 2019
@avli
Copy link
Copy Markdown
Owner

avli commented Mar 8, 2019

Makes perfect sense. Thank you!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants