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
I just noticed this, because:
I was using v0.1.x branch in my cargo.toml, and it's been 8 months, so I've decided to check the release notes once more. After couldn't see the new feature in the release notes, I've decided to check commits, and then found out that with subscriber-0.3.16, this feature seems to be in the code for the commit used for this release. However, there are no mention of this feature, nor the contributors in the release notes.
The text was updated successfully, but these errors were encountered:
I probably confused myself. When I browse the files of commit that is used for 0.3.16 via GitHub UI, the changes of max_n_files are there in appender.
However, in the source-code in my project, they are not there.
Don't know how to interpret this 🤷
tracing-appender and tracing-subscriber are separate crates. The tracing-subscriber 0.3.16 release will not contain features added to tracing-appender.
We need to release a new version of tracing-appender before this change will become available.
Bug Report
For this release: https://github.com/tokio-rs/tracing/releases/tag/tracing-subscriber-0.3.16
I think the feature of
keeping max N files
with this PR: #2323is missed.
I just noticed this, because:
I was using
v0.1.x
branch in my cargo.toml, and it's been 8 months, so I've decided to check the release notes once more. After couldn't see the new feature in the release notes, I've decided to check commits, and then found out that withsubscriber-0.3.16
, this feature seems to be in the code for the commit used for this release. However, there are no mention of this feature, nor the contributors in the release notes.The text was updated successfully, but these errors were encountered: