Open
Conversation
3058a16 to
6b8b4e2
Compare
6b8b4e2 to
a14558a
Compare
a14558a to
6f641d8
Compare
90c8250 to
146375f
Compare
146375f to
7f43292
Compare
7f43292 to
ea3b3d9
Compare
ea3b3d9 to
78df69b
Compare
This file contains hidden or 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
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.
This PR contains the following updates:
0.1.37→0.1.440.3.17→0.3.22Release Notes
tokio-rs/tracing (tracing)
v0.1.44: tracing 0.1.44Compare Source
Fixed
record_allpanic (#3432)Changed
tracing-core: updated to 0.1.36 (#3440)v0.1.43: tracing 0.1.43Compare Source
Important
The previous release 0.1.42 was yanked because #3382 was a breaking change.
See further details in #3424. This release contains all the changes from that
version, plus a revert for the problematic part of the breaking PR.
Fixed
valuesetmacro sanitary" (#3425)v0.1.42: tracing 0.1.42Compare Source
Important
The
Span::record_allmethod has been removed from the documented API. Itwas always unsuable via the documented API as it requried a
ValueSetwhichhas no publically documented constructors. The method remains, but should not
be used outside of
tracingmacros.Added
record_all!macro for recording multiple values in one call (#3227)Changed
tracing-core: updated to 0.1.35 (#3414)tracing-attributes: updated to 0.1.31 (#3417)Fixed
event!(#2983)release_max_level_*not set (#3373)valuesetmacro sanitary (#3382)Documented
dynkeyword inVisitdocumentation code sample (#3387)v0.1.41: tracing 0.1.41Compare Source
[ crates.io ] | [ docs.rs ]
This release updates the
tracing-coredependency to v0.1.33 andthe
tracing-attributesdependency to v0.1.28.Added
Field(#2820)&[u8]to be recorded as event/span field (#2954)Changed
thread_locals when possible (#2838)Fixed
register_callsiteerror (#2938)targetandname(#2941)v0.1.40: tracing 0.1.40Compare Source
This release fixes a potential stack use-after-free in the
Instrument::into_innermethod. Only uses of this method are affected by thisbug.
Fixed
mem::ManuallyDropinstead ofmem::forgetinInstrument::into_inner(#2765)
Thanks to @cramertj and @manishearth for finding and fixing this issue!
v0.1.39: tracing 0.1.39Compare Source
This release adds several additional features to the
tracingmacros. Inaddition, it updates the
tracing-coredependency to v0.1.32 andthe
tracing-attributesdependency to v0.1.27.Added
ValueSets of any length (#2508)Changed
tracing-attributes: updated to 0.1.27tracing-core: updated to 0.1.32Fixed
(#2621, #2757)
clippy::let_with_type_underscore] in macro-generatedcode ([#2609])
unknown_lintsin macro-generated code (#2626)#[instrument]when the"log"feature is enabled (#2599)
Documented
axum-insightsto relevant crates. (#2713)clippy-tracingto related crates (#2628)tracing-cloudwatchto related crates (#2667)tracing-etwrepo (#2602)v0.1.38: tracing 0.1.38Compare Source
This
tracingrelease changes theDropimplementation forInstrumentedFutures so that the attachedSpanis entered when dropping theFuture. Thismeans that events emitted by the
Future'sDropimplementation will now berecorded within its
Span. It also adds#[inline]hints to methods called inthe
event!macro's expansion, for an improvement in both binary size andperformance.
Additionally, this release updates the
tracing-attributesdependency tov0.1.24, which updates the
syndependency to v2.x.x.tracing-attributesv0.1.24 also includes improvements to the#[instrument]macro; see the
tracing-attributes0.1.24 release notes fordetails.
Added
Instrumentedfutures will now enter the attachedSpanin theirDropimplementation, allowing events emitted when dropping the future to occur
within the span (#2562)
#[inline]attributes for methods called by theevent!macros, makinggenerated code smaller (#2555)
levelargument to#[instrument(err)]and#[instrument(ret)]to override the level ofthe generated return value event (#2335)
#[instrument]is added to aconst fn(#2418)
Changed
tracing-attributes: updated to 0.1.24cfg-ifdependency (#2553)syndependency to 2.0 (#2516)Fixed
clippy::unreachablewarnings in#[instrument]-generated code (#2356)syndependency (#2530)Documented
#[instrument(err)](#2433)#[instrument](#2350)Thanks to @nitnelave, @jsgf, @Abhicodes-crypto, @LukeMathWalker, @andrewpollack,
@quad, @klensy, @davidpdrsn, @dbidwell94, @ldm0, @NobodyXu, @ilsv, and @daxpedda
for contributing to this release!
Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.
This PR was generated by Mend Renovate. View the repository job log.