macros: fix breakage in experimental tracing-macros crate (#882)

The `tracing-macros` crate uses internal `tracing` APIs that are
unstable. These APIs changed in 0.1.18 (not a breaking change, since
they are explicitly not stable API). `tracing-macros` needed to be
updated to use the new versions of the internal APIs.

As a side note, I'm surprised this wasn't caught before merging the
branch, and only happened on `master`. Are we not checking all crates
for PR builds? If so, we should probably fix that.

Signed-off-by: Eliza Weisman <eliza@buoyant.io>
This commit is contained in:
Eliza Weisman 2020-08-03 12:28:19 -07:00 committed by GitHub
parent c9f8b6dbe9
commit a4069486b4
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
2 changed files with 2 additions and 2 deletions

View File

@ -17,7 +17,7 @@ keywords = ["logging", "tracing"]
license = "MIT"
[dependencies]
tracing = "0.1"
tracing = "0.1.18"
[dev-dependencies]
tracing-log = "0.1"

View File

@ -37,7 +37,7 @@ macro_rules! dbg {
fields: value,
};
let val = $ex;
if tracing::is_enabled!(callsite) {
if callsite.is_enabled() {
let meta = callsite.metadata();
let fields = meta.fields();
let key = meta