Release a new version of tracing-log with logging fix?
#1884
Comments
bnjbvr
changed the title
tracing-log with https://github.com/tokio-rs/tracing/commit/5fdbcbf61da27ec3e600678121d8c00d2b9b5cb1?tracing-log with 5fdbcbf61da27ec3e600678121d8c00d2b9b5cb1?
bnjbvr
changed the title
tracing-log with 5fdbcbf61da27ec3e600678121d8c00d2b9b5cb1?tracing-log with logging fix?
|
Gentle ping on this topic, is there any way I can help with this? Helping writing release notes, maybe? |
|
I think this change should backported to branch 0.1 instead. 0.2 is still in the development. |
hawkw
added a commit
that referenced
this issue
Apr 21, 2022
# 0.1.3 (April 21st, 2022) ### Added - **log-tracer**: Added `LogTracer::with_interest_cache` to enable a limited form of per-record `Interest` caching for `log` records ([#1636]) ### Changed - Updated minimum supported Rust version (MSRV) to Rust 1.49.0 ([#1913]) ### Fixed - **log-tracer**: Fixed `LogTracer` not honoring `tracing` max level filters ([#1543]) - Broken links in documentation ([#2068], [#2077]) Thanks to @Millione, @teozkr, @koute, @Folyd, and @ben0x539 for contributing to this release! [#1636]: https://github.com/tokio-rs/tracing/pulls/1636 [#1913]: https://github.com/tokio-rs/tracing/pulls/1913 [#1543]: https://github.com/tokio-rs/tracing/pulls/1543 [#2068]: https://github.com/tokio-rs/tracing/pulls/2068 [#2077]: https://github.com/tokio-rs/tracing/pulls/2077 Fixes #1884 Fixes #1664
|
Fixed by #2086 |
kaffarell
pushed a commit
to kaffarell/tracing
that referenced
this issue
May 22, 2024
# 0.1.3 (April 21st, 2022) ### Added - **log-tracer**: Added `LogTracer::with_interest_cache` to enable a limited form of per-record `Interest` caching for `log` records ([tokio-rs#1636]) ### Changed - Updated minimum supported Rust version (MSRV) to Rust 1.49.0 ([tokio-rs#1913]) ### Fixed - **log-tracer**: Fixed `LogTracer` not honoring `tracing` max level filters ([tokio-rs#1543]) - Broken links in documentation ([tokio-rs#2068], [tokio-rs#2077]) Thanks to @Millione, @teozkr, @koute, @Folyd, and @ben0x539 for contributing to this release! [tokio-rs#1636]: https://github.com/tokio-rs/tracing/pulls/1636 [tokio-rs#1913]: https://github.com/tokio-rs/tracing/pulls/1913 [tokio-rs#1543]: https://github.com/tokio-rs/tracing/pulls/1543 [tokio-rs#2068]: https://github.com/tokio-rs/tracing/pulls/2068 [tokio-rs#2077]: https://github.com/tokio-rs/tracing/pulls/2077 Fixes tokio-rs#1884 Fixes tokio-rs#1664
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hi! Seeing that the latest version of tracing-log in Cargo.toml is marked to be 0.2.0, but the latest published version is less than that and is only 0.1.2 on crates.io.
This commit contains an interesting performance fix that never made it to a release, and we would really like to be able to use it in our code base. Any chance a new version of this particular crate including that fix could be published, please? (Either as the 0.2.0 version, or as a 0.1.3 patch version, if the goal is to synchronize a release of 0.2.0 along other 0.2.0 crates)
The text was updated successfully, but these errors were encountered: