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
commented
5 years ago
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.