Avoid stack level to deep when trying to serialize the exception obje…

[mediazard]

Avoid stack level to deep when trying to serialize the exception object in maxretry handler

[michaelklishin]

Never ever bump version in a pull request. It's up to the maintainers to decide when and why it should be done.

[michaelklishin]

@gabrieljoelc @jondot WDYT? This loses exception stack trace information but perhaps in this particular case that's not unreasonable?

[mediazard]

Can you explain better what do you mean ?
https://github.com/reevoo/sneakers/blob/93dca2b31f6116107d00136d055304fa791bb882/lib/sneakers/handlers/maxretry.rb#L147
The reason is still exception object , so why do you think it's not possible to get backtrace info ?
We converted to string just when we assigned to error of data object.

[michaelklishin]

OK, if backtrace is included as a separate field then it's of no concern. Thanks.

[robinbortlik]

@michaelklishin @gabrieljoelc @jondot do we know when this fix will be merged?
Thank you :)

[gabrieljoelc]

I'll bump the gem later