## Motivation
In order to get a compiler warning (or error) when links are broken.
Closes#940
## Solution
- [x] add `deny(broken_intra_doc_links)`
- [x] add a note to the CONTRIBUTING.md documentation on building docs locally
Co-authored-by: Eliza Weisman <eliza@buoyant.io>
Co-authored-by: Joshua Nelson <joshua@yottadb.com>
### Fixed
- Updated `tracing-core` to fix incorrect calculation of the global max
level filter (#908)
### Added
- **attributes**: Support for using `self` in field expressions when
instrumenting `async-trait` functions (#875)
- Several documentation improvements (#832, #881, #896, #897, #911,
#913)
Thanks to @anton-dutov, @nightmared, @mystor, and @toshokan for
contributing to this release!
Signed-off-by: Eliza Weisman <eliza@buoyant.io>
### Fixed
- Fixed a bug where `LevelFilter::OFF` (and thus also the
`static_max_level_off` feature flag) would enable *all* traces,
rather than *none* (#853)
- **log**: Fixed `tracing` macros and `Span`s not checking
`log::max_level` before emitting `log` records (#870)
### Changed
- **macros**: Macros now check the global max level
(`LevelFilter::current`) before the per-callsite cache when
determining if a span or event is enabled. This significantly improves
performance in some use cases (#853)
- **macros**: Simplified the code generated by macro expansion
significantly, which may improve compile times and/or `rustc`
optimizatation of surrounding code (#869, #869)
- **macros**: Macros now check the static max level before checking any
runtime filtering, improving performance when a span or event is
disabled by a `static_max_level_XXX` feature flag (#868)
- `LevelFilter` is now a re-export of the `tracing_core::LevelFilter`
type, it can now be used interchangably with the versions in
`tracing-core` and `tracing-subscriber` (#853)
- Significant performance improvements when comparing `LevelFilter`s and
`Level`s (#853)
- Updated the minimum `tracing-core` dependency to 0.1.12 (#853)
### Added
- **macros**: Quoted string literals may now be used as field names, to
allow fields whose names are not valid Rust identifiers (#790)
- **docs**: Several documentation improvements (#850, #857, #841)
- `LevelFilter::current()` function, which returns the highest level
that any subscriber will enable (#853)
- `Subscriber::max_level_hint` optional trait method, for setting the
value returned by `LevelFilter::current()` (#853)
Thanks to new contributors @cuviper, @ethanboxx, @ben0x539, @dignati,
@colelawrence, and @rbtcollins for helping out with this release!
Signed-off-by: Eliza Weisman <eliza@buoyant.io>
### Changed
- **log**: Moved verbose span enter/exit log records to
"tracing::span::active" target, allowing them to be filtered
separately (#833)
- **log**: All span lifecycle log records without fields now have the
`Trace` log filter, to guard against `log` users enabling them by
default with blanket level filtering (#833)
### Fixed
- **log**/**macros**: Fixed missing implicit imports of the
`tracing::field::debug` and `tracing::field::display` functions inside
the macros when the "log" feature is enabled (#835)
### Added
- **attributes**: Support for arbitrary expressions as fields in
`#[instrument]` (#672)
- **attributes**: `#[instrument]` now emits a compiler warning when
ignoring unrecognized input (#672, #786)
- Improved documentation on using `tracing` in async code (#769)
### Changed
- Updated `tracing-core` dependency to 0.1.11
### Fixed
- **macros**: Excessive monomorphization in macros, which could lead to
longer compilation times (#787)
- **log**: Compiler warnings in macros when `log` or `log-always` features
are enabled (#753)
- Compiler error when `tracing-core/std` feature is enabled but
`tracing/std` is not (#760)
Thanks to @nagisa, and everyone who contributed to the new `tracing-core`
and `tracing-attributes` versions, for contributing to this release!
# 0.1.15 (June 2, 2020)
### Changed
- **macros**: Replaced use of legacy `local_inner_macros` with
`$crate::` (#740)
### Added
- Docs fixes and improvements (#742, #731, #730)
Thanks to @bnjjj, @blaenk, and @LukeMathWalker for contributing to this
release!
Signed-off-by: Eliza Weisman <eliza@buoyant.io>
# 0.1.14 (May 14, 2020)
### Added
- **log**: When using the [`log`] compatibility feature alongside a
`tracing` `Subscriber`, log records for spans now include span IDs
(#613)
- **attributes**: Support for using `#[instrument]` on methods that are
part of [`async-trait`] trait implementations (#711)
- **attributes**: Optional `#[instrument(err)]` argument to
automatically emit an event if an instrumented function returns
`Err` (#637)
- Added `#[must_use]` attribute to the guard returned by
`subscriber::set_default` (#685)
### Changed
- **log**: Made [`log`] records emitted by spans much less noisy when
span IDs are not available (#613)
### Fixed
- Several typos in the documentation (#656, #710, #715)
Thanks to @FintanH, @shepmaster, @inanna-malick, @zekisharif, @bkchr,
@majecty, @ilana and @nightmared for contributing to this release!
[`async-trait`]: https://crates.io/crates/async-traite!
[`log`]: https://crates.io/crates/log
## Motivation
There are unnecessary spaces. Also, there is a point that requires space.
* chore: Remove duplicated spaces
* chore: Add space to make code consistent
* subscriber: add less-verbose configuration APIs
Signed-off-by: Eliza Weisman <eliza@buoyant.io>
* even nicer easymode
Signed-off-by: Eliza Weisman <eliza@buoyant.io>
* wip## Motivation
Users have said fairly frequently that configuring new subscribers in an
application is unnecessarily verbose and confusing. We should try to
make this nicer, especially as it's a common "on ramp" for new `tracing`
users.
## Solution
This branch adds new APIs, inspired by `tonic` and `warp`, that should
make setting up a subscriber a little less verbose. This includes:
- Many modules in `tracing-subscriber` now expose free functions
that construct default instances of various types. This makes
configuring subscribers using these types more concise, a la `warp`.
- An extension trait for adding `.set_default`, `.init`, and `.try_init`
methods to subscribers. This generalizes the similar functions on
`fmt`'s `SubscriberBuilder` to work with other subscribers.
All the old APIs are still left as they were previously. The new APIs
just provide shorthand for them.
Signed-off-by: Eliza Weisman <eliza@buoyant.io>
