Add traceback data to error response when exceptions are raised

[pipermerriam]

What was wrong

Sometimes when an exception occurs on the server side the error response doesn't provide enough context to know where the error actually occurred. Currently the server returns the str(e) where e is the exception which was raised.

How was it fixed.

Added another key to the error data 'traceback' which contains the printed traceback data for the exception.

Cute animal picture

[pipermerriam]

Please let me know if there is a different way you'd like to go about this (assuming you find the addition useful). I didn't see a clear way to conditionally include this information based on whether the server was running in some sort of DEBUG mode.

[coveralls]

Coverage increased (+0.001%) to 99.618% when pulling 21d4ca7 on pipermerriam:piper/more-detailed-information-from-errors into 5605dc5 on pavlov99:master.

[pipermerriam]

Just checking on whether there is any status update on this.

[pavlov99]

Hi, @pipermerriam

Sorry for my late update. I'm checking it out.
My main concern is in security here. If a server would send traceback on every error, it could be a potential loophole. Backend side should be fixed instead.

[pipermerriam]

Understood. What do you think about enabling this with some sort of flag? Something like JSONRPCResponseManager.handle(..., debug=True)