Commit 14c1ec2
authored
fix(deps): update dependency io.perfmark:perfmark-api to v0.26.0 (#8751)
[](https://renovatebot.com)
This PR contains the following updates:
| Package | Change | Age | Adoption | Passing | Confidence |
|---|---|---|---|---|---|
| [io.perfmark:perfmark-api](https://togithub.com/perfmark/perfmark) | `0.25.0` -> `0.26.0` | [](https://docs.renovatebot.com/merge-confidence/) | [](https://docs.renovatebot.com/merge-confidence/) | [](https://docs.renovatebot.com/merge-confidence/) | [](https://docs.renovatebot.com/merge-confidence/) |
---
### Release Notes
<details>
<summary>perfmark/perfmark</summary>
### [`v0.26.0`](https://togithub.com/perfmark/perfmark/releases/tag/v0.26.0): Release 0.26.0
[Compare Source](https://togithub.com/perfmark/perfmark/compare/v0.25.0...v0.26.0)
##### API Changes
- `PerfMark.setEnabled()` now returns if setting the value succeeded. ([#​181](https://togithub.com/perfmark/perfmark/issues/181)).
##### Implementation Improvements
- Added work arounds for Java 19's Virtual threads, which may not be able to
use Thread Local storage. If this is the case, PerfMark attempts to
emulate thread local trace buffers using a concurrent map.
- Trace storage now more eagerly removes storage when it find the thread
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.
- Added Methods to `Storage` for clearing thread local and global storage ([#​177](https://togithub.com/perfmark/perfmark/issues/177))
- `Storage.clearLocalStorage()` enables individual threads to clear their storage
- `Storage.clearGlobalIndex()` marks storage as SoftlyReachable where possible
It can be used to indiciate that future calls to `Storage.read()` should not
include data after the point that the global index was cleared. Both
`clearLocalStorage` and `clearGlobalIndex` can be used to remove old trace
data.
- `LocalMarkHolder` was added to enter and exit critical sections of of
MarkHolder 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.
</details>
---
### 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.
---
- [ ] <!-- rebase-check -->If you want to rebase/retry this PR, check this box
---
This PR has been generated by [Mend Renovate](https://www.mend.io/free-developer-tools/renovate/). View repository job log [here](https://app.renovatebot.com/dashboard#github/googleapis/google-cloud-java).
<!--renovate-debug:eyJjcmVhdGVkSW5WZXIiOiIzNC4xOS4wIiwidXBkYXRlZEluVmVyIjoiMzQuMTkuMCJ9-->1 parent 6ce987f commit 14c1ec2
1 file changed
+1
-1
lines changed| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
34 | 34 | | |
35 | 35 | | |
36 | 36 | | |
37 | | - | |
| 37 | + | |
38 | 38 | | |
39 | 39 | | |
40 | 40 | | |
| |||
0 commit comments