Bump lib.resilience4j.version from 2.2.0 to 2.3.0

[dependabot]

Bumps lib.resilience4j.version from 2.2.0 to 2.3.0.
Updates io.github.resilience4j:resilience4j-all from 2.2.0 to 2.3.0

Release notes

Sourced from io.github.resilience4j:resilience4j-all's releases.

v2.3.0

Enhancements

• Issue #2234: Allow passing custom Clock to CircuitBreaker without needing to use internal API.
• Issue #2131: Added support for RxJava3 in Spring projects.
• Issue #2029: Include decorateSupplier as a Retry instance method.
• Issue #2246: Add handling for the case where a non-checked retry consumer is interrupted during sleep.
• Issue #2245: Refactor Retry#executeSuspendExecute condition to enhance consistency with FlowRetry.
• Issue #2232: Convert Synchronized to ReentrantLock to avoid virtual-thread pinning issues.
• Issue #2241: Implement a lock-free sliding window for internal CircuitBreaker metrics.
• Issue #2239: Add a Clock to CircuitBreakerConfig and utilize it in the state machine.
• Issue #2200: Ignore unknown exceptions in CircuitBreaker configuration.
• Issue #2233: Improve exception message for failure rate threshold in CircuitBreaker configuration.
• Issue #1404: Configure exponential backoff or randomized wait duration if base configuration allows it.
• Issue #2179: Ensure RateLimiter.executeSuspendFunction respects drainPermissionsOnResult in the configuration.
• Issue #2152: Ensure the randomize function always returns a number greater than 1.0.
• Issue #2130: Add support for Feign 12.5+.
• Issue #2121: Specify required RateLimiter permits in annotations.

Bugs

• Issue #2243: Fixed potential memory leak in DefaultEventConsumerRegistry.
• Issue #2209: Resolved issue where CompletionStage does not complete on user-supplied predicate failures.
• Issue #2190: Fixed StackOverflowError and circular reference in CircuitBreaker configuration handling.
• Issue #2175: Fixed validation error message for slowCallDurationThreshold.

Changelog

Sourced from io.github.resilience4j:resilience4j-all's changelog.

=== Version 2.2.0

==== Enhancements

• Support Micronaut 4
• Issue #1962: Added apache commons configuration based registries

==== Bugs

• Issue #2052: Support class name using SpEL expression at @​Circuitbreaker name field enhancement
• Issue #2040: ThreadPoolBulkhead always uses the "default" configuration in micronaut application bug
• Issue #2037: Removing stale retry configurations from configuration map enhancement
• Issue #1625: New module that collects overall information enhancement
• Issue #1565: Do not retry if IntervalFunction returns interval less than 0
• Issue #1865: Timelimiter always uses the "default" configuration in micronaut application
• Issue #2038: java.lang.StackOverflowError due to infinite loop in CircuitBreakerStateMachine$OpenState.tryAcquirePermission

=== Version 2.3.0

==== Enhancements

• Issue #2234: Allow passing custom Clock to CircuitBreaker without needing to use internal API.
• Issue #2131: Added support for RxJava3 in Spring projects.
• Issue #2029: Include decorateSupplier as a Retry instance method.
• Issue #2246: Add handling for the case where a non-checked retry consumer is interrupted during sleep.
• Issue #2245: Refactor Retry#executeSuspendExecute condition to enhance consistency with FlowRetry.
• Issue #2232: Convert Synchronized to ReentrantLock to avoid virtual-thread pinning issues.
• Issue #2241: Implement a lock-free sliding window for internal CircuitBreaker metrics.
• Issue #2239: Add a Clock to CircuitBreakerConfig and utilize it in the state machine.
• Issue #2200: Ignore unknown exceptions in CircuitBreaker configuration.
• Issue #2233: Improve exception message for failure rate threshold in CircuitBreaker configuration.
• Issue #1404: Configure exponential backoff or randomized wait duration if base configuration allows it.
• Issue #2179: Ensure RateLimiter.executeSuspendFunction respects drainPermissionsOnResult in the configuration.
• Issue #2152: Ensure the randomize function always returns a number greater than 1.0.
• Issue #2130: Add support for Feign 12.5+.
• Issue #2121: Specify required RateLimiter permits in annotations.

==== Bugs

• Issue #2243: Fixed potential memory leak in DefaultEventConsumerRegistry.
• Issue #2209: Resolved issue where CompletionStage does not complete on user-supplied predicate failures.
• Issue #2190: Fixed StackOverflowError and circular reference in CircuitBreaker configuration handling.
• Issue #2175: Fixed validation error message for slowCallDurationThreshold.

Commits

• c2c6575 Prepare release 2.3.0
• d0d150f Lock free sliding window for internal CircutBreaker metrics (#2241)
• 9dd0e6b Feature #2200: Ignore Unknown Exceptions in Circuit Breaker Configuration (#2...
• 1318708 Issue #2243: DefaultEventConsumerRegistry could cause memory leak (#2244)
• 4b9614b Closes #Issue 2246 and adds handling for the case non checked retry consumer ...
• ab0b708 Convert syncronized to ReentrantLock to avoid virtual-thread pinned issues (#...
• 5c4281a Refactor Retry#executeSuspendExecute if condition to enhance consistency with...
• fd7c273 Issue #2235: add retryOnResult support to decorateRunnable and decorateChecke...
• 249f2aa Issue #2234: Add a Clock to CircuitBreakerConfig, use it in the state machine...
• ce6cf63 improve exception message, add test (#2222)
• Additional commits viewable in compare view

Updates io.github.resilience4j:resilience4j-retry from 2.2.0 to 2.3.0

Release notes

Sourced from io.github.resilience4j:resilience4j-retry's releases.

v2.3.0

Enhancements

• Issue #2234: Allow passing custom Clock to CircuitBreaker without needing to use internal API.
• Issue #2131: Added support for RxJava3 in Spring projects.
• Issue #2029: Include decorateSupplier as a Retry instance method.
• Issue #2246: Add handling for the case where a non-checked retry consumer is interrupted during sleep.
• Issue #2245: Refactor Retry#executeSuspendExecute condition to enhance consistency with FlowRetry.
• Issue #2232: Convert Synchronized to ReentrantLock to avoid virtual-thread pinning issues.
• Issue #2241: Implement a lock-free sliding window for internal CircuitBreaker metrics.
• Issue #2239: Add a Clock to CircuitBreakerConfig and utilize it in the state machine.
• Issue #2200: Ignore unknown exceptions in CircuitBreaker configuration.
• Issue #2233: Improve exception message for failure rate threshold in CircuitBreaker configuration.
• Issue #1404: Configure exponential backoff or randomized wait duration if base configuration allows it.
• Issue #2179: Ensure RateLimiter.executeSuspendFunction respects drainPermissionsOnResult in the configuration.
• Issue #2152: Ensure the randomize function always returns a number greater than 1.0.
• Issue #2130: Add support for Feign 12.5+.
• Issue #2121: Specify required RateLimiter permits in annotations.

Bugs

• Issue #2243: Fixed potential memory leak in DefaultEventConsumerRegistry.
• Issue #2209: Resolved issue where CompletionStage does not complete on user-supplied predicate failures.
• Issue #2190: Fixed StackOverflowError and circular reference in CircuitBreaker configuration handling.
• Issue #2175: Fixed validation error message for slowCallDurationThreshold.

Changelog

Sourced from io.github.resilience4j:resilience4j-retry's changelog.

=== Version 2.2.0

==== Enhancements

• Support Micronaut 4
• Issue #1962: Added apache commons configuration based registries

==== Bugs

• Issue #2052: Support class name using SpEL expression at @​Circuitbreaker name field enhancement
• Issue #2040: ThreadPoolBulkhead always uses the "default" configuration in micronaut application bug
• Issue #2037: Removing stale retry configurations from configuration map enhancement
• Issue #1625: New module that collects overall information enhancement
• Issue #1565: Do not retry if IntervalFunction returns interval less than 0
• Issue #1865: Timelimiter always uses the "default" configuration in micronaut application
• Issue #2038: java.lang.StackOverflowError due to infinite loop in CircuitBreakerStateMachine$OpenState.tryAcquirePermission

=== Version 2.3.0

==== Enhancements

• Issue #2234: Allow passing custom Clock to CircuitBreaker without needing to use internal API.
• Issue #2131: Added support for RxJava3 in Spring projects.
• Issue #2029: Include decorateSupplier as a Retry instance method.
• Issue #2246: Add handling for the case where a non-checked retry consumer is interrupted during sleep.
• Issue #2245: Refactor Retry#executeSuspendExecute condition to enhance consistency with FlowRetry.
• Issue #2232: Convert Synchronized to ReentrantLock to avoid virtual-thread pinning issues.
• Issue #2241: Implement a lock-free sliding window for internal CircuitBreaker metrics.
• Issue #2239: Add a Clock to CircuitBreakerConfig and utilize it in the state machine.
• Issue #2200: Ignore unknown exceptions in CircuitBreaker configuration.
• Issue #2233: Improve exception message for failure rate threshold in CircuitBreaker configuration.
• Issue #1404: Configure exponential backoff or randomized wait duration if base configuration allows it.
• Issue #2179: Ensure RateLimiter.executeSuspendFunction respects drainPermissionsOnResult in the configuration.
• Issue #2152: Ensure the randomize function always returns a number greater than 1.0.
• Issue #2130: Add support for Feign 12.5+.
• Issue #2121: Specify required RateLimiter permits in annotations.

==== Bugs

• Issue #2243: Fixed potential memory leak in DefaultEventConsumerRegistry.
• Issue #2209: Resolved issue where CompletionStage does not complete on user-supplied predicate failures.
• Issue #2190: Fixed StackOverflowError and circular reference in CircuitBreaker configuration handling.
• Issue #2175: Fixed validation error message for slowCallDurationThreshold.

Commits

• c2c6575 Prepare release 2.3.0
• d0d150f Lock free sliding window for internal CircutBreaker metrics (#2241)
• 9dd0e6b Feature #2200: Ignore Unknown Exceptions in Circuit Breaker Configuration (#2...
• 1318708 Issue #2243: DefaultEventConsumerRegistry could cause memory leak (#2244)
• 4b9614b Closes #Issue 2246 and adds handling for the case non checked retry consumer ...
• ab0b708 Convert syncronized to ReentrantLock to avoid virtual-thread pinned issues (#...
• 5c4281a Refactor Retry#executeSuspendExecute if condition to enhance consistency with...
• fd7c273 Issue #2235: add retryOnResult support to decorateRunnable and decorateChecke...
• 249f2aa Issue #2234: Add a Clock to CircuitBreakerConfig, use it in the state machine...
• ce6cf63 improve exception message, add test (#2222)
• Additional commits viewable in compare view

Updates io.github.resilience4j:resilience4j-micrometer from 2.2.0 to 2.3.0

Release notes

Sourced from io.github.resilience4j:resilience4j-micrometer's releases.

v2.3.0

Enhancements

• Issue #2234: Allow passing custom Clock to CircuitBreaker without needing to use internal API.
• Issue #2131: Added support for RxJava3 in Spring projects.
• Issue #2029: Include decorateSupplier as a Retry instance method.
• Issue #2246: Add handling for the case where a non-checked retry consumer is interrupted during sleep.
• Issue #2245: Refactor Retry#executeSuspendExecute condition to enhance consistency with FlowRetry.
• Issue #2232: Convert Synchronized to ReentrantLock to avoid virtual-thread pinning issues.
• Issue #2241: Implement a lock-free sliding window for internal CircuitBreaker metrics.
• Issue #2239: Add a Clock to CircuitBreakerConfig and utilize it in the state machine.
• Issue #2200: Ignore unknown exceptions in CircuitBreaker configuration.
• Issue #2233: Improve exception message for failure rate threshold in CircuitBreaker configuration.
• Issue #1404: Configure exponential backoff or randomized wait duration if base configuration allows it.
• Issue #2179: Ensure RateLimiter.executeSuspendFunction respects drainPermissionsOnResult in the configuration.
• Issue #2152: Ensure the randomize function always returns a number greater than 1.0.
• Issue #2130: Add support for Feign 12.5+.
• Issue #2121: Specify required RateLimiter permits in annotations.

Bugs

• Issue #2243: Fixed potential memory leak in DefaultEventConsumerRegistry.
• Issue #2209: Resolved issue where CompletionStage does not complete on user-supplied predicate failures.
• Issue #2190: Fixed StackOverflowError and circular reference in CircuitBreaker configuration handling.
• Issue #2175: Fixed validation error message for slowCallDurationThreshold.

Changelog

Sourced from io.github.resilience4j:resilience4j-micrometer's changelog.

=== Version 2.2.0

==== Enhancements

• Support Micronaut 4
• Issue #1962: Added apache commons configuration based registries

==== Bugs

• Issue #2052: Support class name using SpEL expression at @​Circuitbreaker name field enhancement
• Issue #2040: ThreadPoolBulkhead always uses the "default" configuration in micronaut application bug
• Issue #2037: Removing stale retry configurations from configuration map enhancement
• Issue #1625: New module that collects overall information enhancement
• Issue #1565: Do not retry if IntervalFunction returns interval less than 0
• Issue #1865: Timelimiter always uses the "default" configuration in micronaut application
• Issue #2038: java.lang.StackOverflowError due to infinite loop in CircuitBreakerStateMachine$OpenState.tryAcquirePermission

=== Version 2.3.0

==== Enhancements

• Issue #2234: Allow passing custom Clock to CircuitBreaker without needing to use internal API.
• Issue #2131: Added support for RxJava3 in Spring projects.
• Issue #2029: Include decorateSupplier as a Retry instance method.
• Issue #2246: Add handling for the case where a non-checked retry consumer is interrupted during sleep.
• Issue #2245: Refactor Retry#executeSuspendExecute condition to enhance consistency with FlowRetry.
• Issue #2232: Convert Synchronized to ReentrantLock to avoid virtual-thread pinning issues.
• Issue #2241: Implement a lock-free sliding window for internal CircuitBreaker metrics.
• Issue #2239: Add a Clock to CircuitBreakerConfig and utilize it in the state machine.
• Issue #2200: Ignore unknown exceptions in CircuitBreaker configuration.
• Issue #2233: Improve exception message for failure rate threshold in CircuitBreaker configuration.
• Issue #1404: Configure exponential backoff or randomized wait duration if base configuration allows it.
• Issue #2179: Ensure RateLimiter.executeSuspendFunction respects drainPermissionsOnResult in the configuration.
• Issue #2152: Ensure the randomize function always returns a number greater than 1.0.
• Issue #2130: Add support for Feign 12.5+.
• Issue #2121: Specify required RateLimiter permits in annotations.

==== Bugs

• Issue #2243: Fixed potential memory leak in DefaultEventConsumerRegistry.
• Issue #2209: Resolved issue where CompletionStage does not complete on user-supplied predicate failures.
• Issue #2190: Fixed StackOverflowError and circular reference in CircuitBreaker configuration handling.
• Issue #2175: Fixed validation error message for slowCallDurationThreshold.

Commits

• c2c6575 Prepare release 2.3.0
• d0d150f Lock free sliding window for internal CircutBreaker metrics (#2241)
• 9dd0e6b Feature #2200: Ignore Unknown Exceptions in Circuit Breaker Configuration (#2...
• 1318708 Issue #2243: DefaultEventConsumerRegistry could cause memory leak (#2244)
• 4b9614b Closes #Issue 2246 and adds handling for the case non checked retry consumer ...
• ab0b708 Convert syncronized to ReentrantLock to avoid virtual-thread pinned issues (#...
• 5c4281a Refactor Retry#executeSuspendExecute if condition to enhance consistency with...
• fd7c273 Issue #2235: add retryOnResult support to decorateRunnable and decorateChecke...
• 249f2aa Issue #2234: Add a Clock to CircuitBreakerConfig, use it in the state machine...
• ce6cf63 improve exception message, add test (#2222)
• 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)

[codacy-production]

Coverage summary from Codacy

See diff coverage on Codacy

Coverage variation	Diff coverage
✅ +18.34% (target: -1.00%)	✅ ∅ (target: 70.00%)

Coverage variation details

	Coverable lines	Covered lines	Coverage
Common ancestor commit (63ed452)	201	132	65.67%
Head commit (d06a01d)	6899 (+6698)	5796 (+5664)	84.01% (+18.34%)

Coverage variation is the difference between the coverage for the head and common ancestor commits of the pull request branch: <coverage of head commit> - <coverage of common ancestor commit>

Diff coverage details

	Coverable lines	Covered lines	Diff coverage
Pull request (#1625)	0	0	∅ (not applicable)

Diff coverage is the percentage of lines that are covered by tests out of the coverable lines that the pull request added or modified: <covered lines added or modified>/<coverable lines added or modified> * 100%

See your quality gate settings    Change summary preferences

_{Codacy stopped sending the deprecated coverage status on June 5th, 2024. Learn more}