-
Notifications
You must be signed in to change notification settings - Fork 139
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
remove pkarr publish backtrace on error #2316
Comments
This is a new feature of anyhow. It now will always attach backtraces and print them when RUST_BACKTRACE=1 is set. From https://crates.io/crates/anyhow:
So we either don't print anyhow errors anymore, or just change CI to set I think maybe the latter is the way to go? We got tons of places in the code where we are printing errors in log statements. And people won't run into this if they don't set RUST_BACKTRACE=1. |
@Arqu this would be just adding RUST_LIB_BACKTRACE=0 to all ci yaml files where RUST_LOG is set, right? E.g. here:
|
Yeah, reading the docs you mentioned seems like doing It does result in the unfortunate situation where we don't see other lib backtraces, but we already knew that I guess. |
at least in ci there is a constant emission of these:
if this is ever triggered for an user this is more than 120 lines in a single warn that look like a panic. In ci this is very annoying, for an user this would look terribly worrisome and provides imo no actual extra information that can be used to know why the publish failed
This is emitted in
discovery service produced error
and
Failed to publish to pkarr
The text was updated successfully, but these errors were encountered: