You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi, when you for some reason have Arc<eyre::Report> and try to wrap it into a eyre::Report using eyre!(...), it loses traces from the report (previously added with wrap_err, etc.).
Why would you have Arc<eyre::Report> you ask? For example moka returns Arc wrapped errors from some of its functions.
The text was updated successfully, but these errors were encountered:
I believe this is happening because the macro can only tell that your type implements Display, and so it only uses that interface for reporting the inner error which ends up only printing the outermost error message. We can probably modify the auto deref specialization in the macro to also account for this and more smoothly handle Arc, tho it would be very specific to this exact use case which feels like a yellow flag design wise for me. I want to take more time to think before deciding to more forward in this direction.
Hi, when you for some reason have
Arc<eyre::Report>
and try to wrap it into aeyre::Report
usingeyre!(...)
, it loses traces from the report (previously added withwrap_err
, etc.).Why would you have
Arc<eyre::Report>
you ask? For examplemoka
returnsArc
wrapped errors from some of its functions.The text was updated successfully, but these errors were encountered: