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 Sep 13, 2023. It is now read-only.
As it is right now, the -vvv enables logging only for the main crate. For some use-cases, the ability to log everything would make more sense. Any way to achieve it?
Right now even RUST_LOG no longer works.
The text was updated successfully, but these errors were encountered:
dpc
added a commit
to dpc/quicli
that referenced
this issue
Aug 14, 2018
Searched specifically to see if there was a ticket for this. I had to stop using quicli for a few applications because the regular debugging information provided by fn main() -> Result<> {} was better. I forget what the issue was, either the quicli output didn't include a backtrace, the full cause list, or logging information for libraries, or some combination of them.
But basically I started doing this whenever I needed to be sure I would be able to see all the debugging output, because quicli seemed to silently hide stuff.
Otherwise, I was really happy with quicli.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
As it is right now, the
-vvv
enables logging only for the main crate. For some use-cases, the ability to log everything would make more sense. Any way to achieve it?Right now even
RUST_LOG
no longer works.The text was updated successfully, but these errors were encountered: