fix(deps): update rust crate tracing to 0.1.40 #16
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.40
Release Notes
tokio-rs/tracing (tracing)
v0.1.40
: tracing 0.1.40Compare Source
This release fixes a potential stack use-after-free in the
Instrument::into_inner
method. Only uses of this method are affected by thisbug.
Fixed
mem::ManuallyDrop
instead ofmem::forget
inInstrument::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
tracing
macros. Inaddition, it updates the
tracing-core
dependency to v0.1.32 andthe
tracing-attributes
dependency to v0.1.27.Added
ValueSet
s 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_lints
in macro-generated code (#2626)#[instrument]
when the"log"
feature is enabled (#2599)
Documented
axum-insights
to relevant crates. (#2713)clippy-tracing
to related crates (#2628)tracing-cloudwatch
to related crates (#2667)tracing-etw
repo (#2602)v0.1.38
: tracing 0.1.38Compare Source
This
tracing
release changes theDrop
implementation forInstrumented
Future
s so that the attachedSpan
is entered when dropping theFuture
. Thismeans that events emitted by the
Future
'sDrop
implementation 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-attributes
dependency tov0.1.24, which updates the [
syn
][syn] dependency to v2.x.x.tracing-attributes
v0.1.24 also includes improvements to the#[instrument]
macro; see the
tracing-attributes
0.1.24 release notes fordetails.
Added
Instrumented
futures will now enter the attachedSpan
in theirDrop
implementation, 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)
level
argument 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-if
dependency (#2553)syn
][syn] dependency to 2.0 (#2516)Fixed
clippy::unreachable
warnings in#[instrument]
-generated code (#2356)syn
dependency (#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: Enabled.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR has been generated by Mend Renovate. View repository job log here.