Skip to content
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

subscriber: prepare to release 0.2.0 stable #567

Merged
merged 1 commit into from
Feb 4, 2020
Merged

Conversation

hawkw
Copy link
Member

@hawkw hawkw commented Feb 4, 2020

0.2.0 (February 4, 2020)

Breaking Changes

Added

Changed

Removed

Fixed

0.2.0 (February 4, 2020)

Breaking Changes:

- **fmt**: Renamed `Context` to `FmtContext` (#420, #425)
- **fmt**: Renamed `Builder` to `SubscriberBuilder` (#420)
- **filter**: Removed `Filter`. Use `EnvFilter` instead (#434)

Added:

- **registry**: `Registry`, a reusable span store that `Layer`s can use
  a high-performance, in-memory store. (#420, #425, #432, #433, #435)
- **registry**: Added `LookupSpan` trait, implemented by `Subscriber`s
  to expose stored span data to `Layer`s (#420)
- **fmt**: Added `fmt::Layer`, to allow composing log formatting with
  other `Layer`s (#420)
- **fmt**: Added support for JSON field and event formatting (#377,
  #415)
- **filter**: Documentation for filtering directives (#554)

Changed:

- **fmt**: Renamed `Context` to `FmtContext` (#420, #425) (BREAKING)
- **fmt**: Renamed `Builder` to `SubscriberBuilder` (#420) (BREAKING)
- **fmt**: Reimplemented `fmt::Subscriber` in terms of the `Registry`
  and `Layer`s (#420)

Removed:

- **filter**: Removed `Filter`. Use `EnvFilter` instead (#434) (BREAKING)

Fixed:

- **fmt**: Fixed memory leaks in the slab used to store per-span data
  (3c35048)
- **fmt**: `fmt::SubscriberBuilder::init` not setting up `log`
  compatibility (#489)
- **fmt**: Spans closed by a child span closing not also closing _their_
  parents (#514)
- **Layer**: Fixed `Layered` subscribers failing to downcast to their
  own type (#549)
- **Layer**: Fixed `Layer::downcast_ref` returning invalid references
  (#454)

Signed-off-by: Eliza Weisman <[email protected]>
@hawkw hawkw added crate/subscriber Related to the `tracing-subscriber` crate kind/maintenance labels Feb 4, 2020
@hawkw hawkw requested a review from a team February 4, 2020 23:01
@hawkw hawkw self-assigned this Feb 4, 2020
Copy link
Member

@LucioFranco LucioFranco left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🚢 it

@davidbarsky davidbarsky self-requested a review February 4, 2020 23:15
@davidbarsky
Copy link
Member

@hawkw
Copy link
Member Author

hawkw commented Feb 4, 2020

@davidbarsky we'll do that in a follow-up when the crate is published; otherwise we'd be breaking the examples.

@davidbarsky
Copy link
Member

@hawkw Merge away!

@hawkw hawkw merged commit 8711f63 into master Feb 4, 2020
hawkw added a commit to hawkw/tracing-gelf that referenced this pull request Feb 5, 2020
`tracing-subscriber` 0.2.0-stable is a major release with several bug
fixes, including fixes for a memory leak in the `Registry` span storage.
Since Cargo cannot automatically update versions ending with `-alpha.X`,
crates depending on earlier `tracing-subscriber` 0.2.0 alpha releases
should update to stable. 

See tokio-rs/tracing#567 for the complete changelog.
hawkw added a commit to hawkw/tracing-opentelemetry that referenced this pull request Feb 5, 2020
`tracing-subscriber` 0.2.0-stable is a major release with several bug
fixes, including fixes for a memory leak in the `Registry` span storage.
Since Cargo cannot automatically update versions ending with `-alpha.X`,
crates depending on earlier `tracing-subscriber` 0.2.0 alpha releases
should update to stable. 

See tokio-rs/tracing#567 for the complete changelog.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
crate/subscriber Related to the `tracing-subscriber` crate kind/maintenance
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants