Bump com.github.chrisvest:stormpot from 2.4 to 4.1

[dependabot]

Bumps com.github.chrisvest:stormpot from 2.4 to 4.1.

Release notes

Sourced from com.github.chrisvest:stormpot's releases.

Stormpot 4.1

This is a bug-fix release, that fixes a data-race bug that can produce a NullPointerException (and in turn potentially stop the background allocator thread) when subscribing to a Completion races with it completing.

What's Changed

• Trim api-changes.json by @​chrisvest in chrisvest/stormpot#206
• Exclude 'stormpot.internal' from revapi by @​chrisvest in chrisvest/stormpot#208
• Add a benchmark where claim and release are done in different threads by @​chrisvest in chrisvest/stormpot#209
• Update the ThreadTransfer benchmark by @​chrisvest in chrisvest/stormpot#210
• Fix data race in StackCompletion by @​chrisvest in chrisvest/stormpot#211
• Small benchmark updates by @​chrisvest in chrisvest/stormpot#212
• Encapsulate the object field in Pooled by @​chrisvest in chrisvest/stormpot#213
• Make it possible to build a Completion from a callback by @​chrisvest in chrisvest/stormpot#214

Full Changelog: chrisvest/stormpot@stormpot-4.0...stormpot-4.1

Stormpot 4.0

This is a major release that adds many features and upgrades the minimum Java version requirement to Java 21.

The most notable features are adding support for virtual threads. The background allocator thread is now a virtual thread by default. There is also a new virtual-thread-safe PoolTap implementation available from Pool.getVirtualThreadSafeTap(). The claim methods on the Pool interface still rely on ThreadLocal variables, however, and should be avoided if you plan to access the pool from virtual threads.

The leak detector is now off by default. The implementation of the leak detector has also changed to make it dramatically more scalable with large pool sizes.

Speaking of large pools, it is now possible to create pools with more than 2 billion objects. It's still recommended to keep pools as small as possible, but if you really need a very large number of objects, it's now possible.

Threaded and inline pools can now change their Allocator implementation after they've been created. This is useful if you want to change how objects of the same type are created. The process of switching allocators is asynchronous and eventual, but more controlled than building this functionality into your Allocator implementation itself. Direct pools cannot switch allocators, because all their objects are given up front when the pool is created, and their objects are assumed to not need any significant lifecycle management from the pool.

This is a major release that breaks API/ABI compatibility, but the changes are fairly small, so migrating an existing code base should not be too much trouble. See api-changes.json for the complete list of compatibility changes.

What's Changed

• Upgrade to Java 21 and Remove asciidoclet by @​chrisvest in chrisvest/stormpot#171
• Make use of new Java language features by @​chrisvest in chrisvest/stormpot#172
• Fix test flakiness by @​chrisvest in chrisvest/stormpot#173
• Move non-tests out of the stormpot test package by @​chrisvest in chrisvest/stormpot#174
• Add a SlotInfo.getCreatedNanoTime and fix flaky test by @​chrisvest in chrisvest/stormpot#175
• Separate API and internals and make tests modular by @​chrisvest in chrisvest/stormpot#176
• Make internal classes final where possible by @​chrisvest in chrisvest/stormpot#177
• New leak detector by @​chrisvest in chrisvest/stormpot#178
• Add a PoolTap that support virtual threads by @​chrisvest in chrisvest/stormpot#179
• Add Java 23 to the PR builds by @​chrisvest in chrisvest/stormpot#180
• Update GitHub Actions by @​chrisvest in chrisvest/stormpot#182

... (truncated)

Commits

• 4034e08 Prepare for releasing 4.1
• 0ba5af1 Make it possible to build a Completion from a callback (#214)
• 2815a23 Make it possible to build a Completion from a callback
• 64073ba Encapsulate the object field in Pooled (#213)
• ab43b7c Encapsulate the object field in Pooled
• 9d7565c Small benchmark updates (#212)
• 5f29c84 Small benchmark updates
• 561af9a Fix data race in StackCompletion (#211)
• bd32c2a Fix data race in StackCompletion
• 804cb56 Update the ThreadTransfer benchmark (#210)
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)