On Decoding error, the Dynosaur Conversions do not propagate error message

[onema]

We've run into a problem when using Meteor and Dynosaur. When there is a conversion error, the exception message is not set in the DecodeError in this line conversions.scala#L23.

When debugging, I observed that the Throwable.detailedMessage field doesn't contain a value, but for some reason, the object contains a message field that includes the error information.

Losing this information makes it very hard to troubleshoot problems with the data and/or the application.,

I will try to set up a simple test case and update this ticket.