Skip to content
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

tracing_subscriber::fmt().init() does not trace debug (does print info) #1908

Closed
EdmundsEcho opened this issue Feb 6, 2022 · 1 comment
Closed

Comments

@EdmundsEcho
Copy link

Bug Report

When the tracer is built using

tracing_subscriber::fmt().init();
// or
tracing_subscriber::fmt().pretty().init(); 

... the debug tracing does not show up.

Version

tracing-subscriber = { version="0.3", features = ["env-filter", "fmt", "std"] }

cargo tree | grep tracing
│   │   │   └── tracing v0.1.29
│   │   │       ├── tracing-attributes v0.1.18 (proc-macro)
│   │   │       └── tracing-core v0.1.21
│   │   ├── tracing v0.1.29 (*)
│   │   └── tracing v0.1.29 (*)
│   │   └── tracing v0.1.29 (*)
├── tracing v0.1.29 (*)
├── tracing-subscriber v0.3.7
│   ├── tracing v0.1.29 (*)
│   ├── tracing-core v0.1.21 (*)
│   └── tracing-log v0.1.2
│       └── tracing-core v0.1.21 (*)

Platform

MacOS 12.1 on M1

Description

The following generates output

✅  tracing::info!("\n 🔑 cookie: {:?}", cookie);

Whereas the following does not

🚫  tracing::debug!("\n 🔑 cookie: {:?}", cookie);

... only when I stop using the fmt() function, does the debug trace information show-up.

✅  tracing_subscriber::fmt::init();

- E

@davidbarsky
Copy link
Member

This is a known issue which is tracked in #1697. I'll close this issue can ask that you follow that one instead.

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

No branches or pull requests

2 participants