Better exception handling in user callbacks #102
Description
Currently, we are just dumping the error message for the user space exception, but it may be quite difficult to locate the location of the problem based on this alone. Information about what call is being made, and perhaps a stack trace would be better?
Solution alternatives
A
Add logging inside of the wrapper layer which dumps a stack trace, and then rethrows to have normal exception handling on the native side as today.
B
Give better error message, e.g. with stack trace encoded, in the joystream-node exception handling. Would not provide genuine stack trace into javascript user callback code, but would include it as a payload.
C
To reconstruct a fresh exception from scratch on the native side with the stack trace of the user land exception.