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
{{ message }}
This repository has been archived by the owner on Aug 1, 2024. It is now read-only.
Similar to my issue for: #32 , it seems color-eyre has started adding in messages about the fact that backtraces are not being captured, compare a message just using 0.5.0:
With one using 0.5.5:
This adds a lot of noise, even more so when there may be multiple errors printed to the screen (since they're "recoverable" cases):
All this extra lines can make it hard to zero in on what's important, even more so when it's repeated multiple times. Is there any chance similar to the capture spantrace message being able to be turned off with some: capture_span_trace_by_default we could get an option for disabling the backtrace output as well?
The text was updated successfully, but these errors were encountered:
Hey again,
Similar to my issue for: #32 , it seems color-eyre has started adding in messages about the fact that backtraces are not being captured, compare a message just using 0.5.0:
With one using 0.5.5:
This adds a lot of noise, even more so when there may be multiple errors printed to the screen (since they're "recoverable" cases):
All this extra lines can make it hard to zero in on what's important, even more so when it's repeated multiple times. Is there any chance similar to the capture spantrace message being able to be turned off with some:
capture_span_trace_by_default
we could get an option for disabling the backtrace output as well?The text was updated successfully, but these errors were encountered: