Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix(deps): update dependency io.perfmark:perfmark-api to v0.26.0 #8751

Conversation

renovate-bot
Copy link
Contributor

Mend Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
io.perfmark:perfmark-api 0.25.0 -> 0.26.0 age adoption passing confidence

Release Notes

perfmark/perfmark

v0.26.0: Release 0.26.0

Compare Source

API Changes
  • PerfMark.setEnabled() now returns if setting the value succeeded. (#​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)
    • 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.

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.


  • If you want to rebase/retry this PR, check this box

This PR has been generated by Mend Renovate. View repository job log here.

@trusted-contributions-gcf trusted-contributions-gcf bot added kokoro:force-run Add this label to force Kokoro to re-run the tests. owlbot:run Add this label to trigger the Owlbot post processor. labels Nov 9, 2022
@gcf-owl-bot gcf-owl-bot bot removed the owlbot:run Add this label to trigger the Owlbot post processor. label Nov 9, 2022
@yoshi-kokoro yoshi-kokoro removed the kokoro:force-run Add this label to force Kokoro to re-run the tests. label Nov 9, 2022
@alicejli alicejli added the automerge Merge the pull request once unit tests and other checks pass. label Nov 9, 2022
@gcf-merge-on-green gcf-merge-on-green bot merged commit 14c1ec2 into googleapis:main Nov 9, 2022
@gcf-merge-on-green gcf-merge-on-green bot removed the automerge Merge the pull request once unit tests and other checks pass. label Nov 9, 2022
@renovate-bot renovate-bot deleted the renovate/io.perfmark-perfmark-api-0.x branch November 9, 2022 16:26
@release-please release-please bot mentioned this pull request Nov 9, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants