-
Notifications
You must be signed in to change notification settings - Fork 734
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
explicitly flush previous BufWriter before dropping #1604
Merged
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
hawkw
approved these changes
Oct 1, 2021
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for the fix, this looks good to me!
hawkw
pushed a commit
that referenced
this pull request
Oct 1, 2021
## Motivation When a `RollingFileAppender` is refreshed, the previous `BufWriter` may encounter and suppress errors in `drop`. From https://doc.rust-lang.org/std/io/struct.BufWriter.html: > It is critical to call flush before BufWriter<W> is dropped. Though > dropping will attempt to flush the contents of the buffer, any errors > that happen in the process of dropping will be ignored. ## Solution Explicitly flush the previous buffer before dropping, printing any error to stderr.
hawkw
pushed a commit
that referenced
this pull request
Oct 1, 2021
## Motivation When a `RollingFileAppender` is refreshed, the previous `BufWriter` may encounter and suppress errors in `drop`. From https://doc.rust-lang.org/std/io/struct.BufWriter.html: > It is critical to call flush before BufWriter<W> is dropped. Though > dropping will attempt to flush the contents of the buffer, any errors > that happen in the process of dropping will be ignored. ## Solution Explicitly flush the previous buffer before dropping, printing any error to stderr.
hawkw
added a commit
that referenced
this pull request
Oct 22, 2021
# 0.2.0 (October 22, 2021) This breaking change release adds support for the new v0.3.x series of `tracing-subscriber`. In addition, it resolves the security advisory for the `chrono` crate, [RUSTSEC-2020-0159]. This release increases the minimum supported Rust version (MSRV) to 1.51.0. ### Breaking Changes - Updated `tracing-subscriber` to v0.3.x ([#1677]) - Changed `NonBlocking::error_counter` to return an `ErrorCounter` type, rather than an `Arc<AtomicU64>` ([#1675]) ### Changed - Updated `tracing-subscriber` to v0.3.x ([#1677]) ### Fixed - **non-blocking**: Fixed compilation on 32-bit targets ([#1675]) - **rolling**: Replaced `chrono` dependency with `time` to resolve [RUSTSEC-2020-0159] ([#1652]) - **rolling**: Fixed an issue where `RollingFileAppender` would fail to print errors that occurred while flushing a previous logfile ([#1604]) Thanks to new contributors @dzvon and @zvkemp for contributing to this release! [RUSTSEC-2020-0159]: https://rustsec.org/advisories/RUSTSEC-2020-0159.html [#1677]: #1677 [#1675]: #1675 [#1652]: #1675 [#1604]: #1604
hawkw
added a commit
that referenced
this pull request
Oct 23, 2021
# 0.2.0 (October 22, 2021) This breaking change release adds support for the new v0.3.x series of `tracing-subscriber`. In addition, it resolves the security advisory for the `chrono` crate, [RUSTSEC-2020-0159]. This release increases the minimum supported Rust version (MSRV) to 1.51.0. ### Breaking Changes - Updated `tracing-subscriber` to v0.3.x ([#1677]) - Changed `NonBlocking::error_counter` to return an `ErrorCounter` type, rather than an `Arc<AtomicU64>` ([#1675]) ### Changed - Updated `tracing-subscriber` to v0.3.x ([#1677]) ### Fixed - **non-blocking**: Fixed compilation on 32-bit targets ([#1675]) - **rolling**: Replaced `chrono` dependency with `time` to resolve [RUSTSEC-2020-0159] ([#1652]) - **rolling**: Fixed an issue where `RollingFileAppender` would fail to print errors that occurred while flushing a previous logfile ([#1604]) Thanks to new contributors @dzvon and @zvkemp for contributing to this release! [RUSTSEC-2020-0159]: https://rustsec.org/advisories/RUSTSEC-2020-0159.html [#1677]: #1677 [#1675]: #1675 [#1652]: #1675 [#1604]: #1604
kaffarell
pushed a commit
to kaffarell/tracing
that referenced
this pull request
May 22, 2024
# 0.2.0 (October 22, 2021) This breaking change release adds support for the new v0.3.x series of `tracing-subscriber`. In addition, it resolves the security advisory for the `chrono` crate, [RUSTSEC-2020-0159]. This release increases the minimum supported Rust version (MSRV) to 1.51.0. ### Breaking Changes - Updated `tracing-subscriber` to v0.3.x ([tokio-rs#1677]) - Changed `NonBlocking::error_counter` to return an `ErrorCounter` type, rather than an `Arc<AtomicU64>` ([tokio-rs#1675]) ### Changed - Updated `tracing-subscriber` to v0.3.x ([tokio-rs#1677]) ### Fixed - **non-blocking**: Fixed compilation on 32-bit targets ([tokio-rs#1675]) - **rolling**: Replaced `chrono` dependency with `time` to resolve [RUSTSEC-2020-0159] ([tokio-rs#1652]) - **rolling**: Fixed an issue where `RollingFileAppender` would fail to print errors that occurred while flushing a previous logfile ([tokio-rs#1604]) Thanks to new contributors @dzvon and @zvkemp for contributing to this release! [RUSTSEC-2020-0159]: https://rustsec.org/advisories/RUSTSEC-2020-0159.html [tokio-rs#1677]: tokio-rs#1677 [tokio-rs#1675]: tokio-rs#1675 [tokio-rs#1652]: tokio-rs#1675 [tokio-rs#1604]: tokio-rs#1604
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Motivation
When a RollingFileAppender is refreshed, the previous
BufWriter
may encounter and suppress errors indrop
.From https://doc.rust-lang.org/std/io/struct.BufWriter.html:
Solution
Explicitly flush the previous buffer before dropping, printing any error to stderr.