fix(deps): update dependency io.perfmark:perfmark-api to v0.26.0 #8751
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.25.0
->0.26.0
Release Notes
perfmark/perfmark
v0.26.0
: Release 0.26.0Compare Source
API Changes
PerfMark.setEnabled()
now returns if setting the value succeeded. (#181).Implementation Improvements
use Thread Local storage. If this is the case, PerfMark attempts to
emulate thread local trace buffers using a concurrent map.
is gone, and is more GC friendly. PerfMark still attempts to preserve
trace data after a thread finishes, but without strongly referring to it.
Unstable API Changes
The following changes are to unstable APIs of PerfMark. This section
describes APIs for advanced users to try out new functionality before
it becomes API stable.
Storage
for clearing thread local and global storage (#177)Storage.clearLocalStorage()
enables individual threads to clear their storageStorage.clearGlobalIndex()
marks storage as SoftlyReachable where possibleIt can be used to indiciate that future calls to
Storage.read()
should notinclude data after the point that the global index was cleared. Both
clearLocalStorage
andclearGlobalIndex
can be used to remove old tracedata.
LocalMarkHolder
was added to enter and exit critical sections of ofMarkHolder mutation. The only implementation currently pulls the MarkHolder
out of thread local storage for editing. However, this designed to work with
other context-specific storage mechanisms, such as Kotlin's Coroutines.
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.
🔕 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.