Skip to content
This repository has been archived by the owner on Aug 1, 2024. It is now read-only.

Ability to silence Backtrace omitted. Error Messaging #65

Closed
Mythra opened this issue Sep 23, 2020 · 3 comments
Closed

Ability to silence Backtrace omitted. Error Messaging #65

Mythra opened this issue Sep 23, 2020 · 3 comments

Comments

@Mythra
Copy link
Contributor

Mythra commented Sep 23, 2020

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:

Old Dev-Loop Error

With one using 0.5.5:

Screenshot from 2020-09-23 10-09-30

This adds a lot of noise, even more so when there may be multiple errors printed to the screen (since they're "recoverable" cases):

Screenshot from 2020-09-23 10-11-52

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?

@yaahc
Copy link
Collaborator

yaahc commented Sep 23, 2020

@Mythra
Copy link
Contributor Author

Mythra commented Sep 23, 2020

Ah I thought I checked and everything! So sorry for missing that. Thank you so much!

@Mythra Mythra closed this as completed Sep 23, 2020
@yaahc
Copy link
Collaborator

yaahc commented Sep 23, 2020

No worries at all :D

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants