Revert change to tracing (#10578)
Although we thought this fixed the bug, it just worked around it, and runnign two copies of tracing in one app is a bad idea. Simplify default RUST_LOG in development to avoid https://github.com/tokio-rs/tracing/issues/2927#issuecomment-2040080189 Release Notes: - N/A
This commit is contained in:
@@ -64,7 +64,7 @@ toml.workspace = true
|
||||
tower = "0.4"
|
||||
tower-http = { workspace = true, features = ["trace"] }
|
||||
tracing = "0.1.40"
|
||||
tracing-subscriber = { git = "https://github.com/tokio-rs/tracing", rev = "tracing-subscriber-0.3.18", features = ["env-filter", "json", "registry", "tracing-log"] } # workaround for https://github.com/tokio-rs/tracing/issues/2927
|
||||
tracing-subscriber = { version = "0.3.18", features = ["env-filter", "json", "registry", "tracing-log"] } # workaround for https://github.com/tokio-rs/tracing/issues/2927
|
||||
util.workspace = true
|
||||
uuid.workspace = true
|
||||
|
||||
|
||||
Reference in New Issue
Block a user