Bump failsafe from 2.4.0 to 2.4.4

[dependabot]

Bumps failsafe from 2.4.0 to 2.4.4.

Changelog

Sourced from failsafe's changelog.

2.4.4

Bug Fixes

• Fixed #298 - Fallback.onFailedAttempt not being called correctly

Improvements

• Fixed #296 - Add Automatic-Module-Name entry to the generated manifest file

API Changes

• Added a generic result type R to ExecutionContext, Execution, AsyncExecution, and AsyncRunnable. This ensures that result types are unified across the API. It does mean that there are a few minor breaking changes to the API:
  • ContextualSupplier now has an additional result type parameter R. Normally this type is used as lambda parameters where the type is inferred, so most users should not be impacted. But any explicit generic declaration of this type will not compile until the new parameter is added.
  • PolicyExecutor, which is part of the SPI, now accepts an additional result type parameter R. This is only relevant for SPI users who are implementing their own Policies.
• Changed FailsafeExecutor.getAsyncExecution to accept AsyncRunnable instead of AsyncSupplier. This is a breaking change for any getAsyncExecution calls, but the fix is to simply remove any return statement. The reason for this change is that the provided object does not need to return a result since the result will already be passed asynchronously to one of the AsyncExecution complete or retry methods.

2.4.3

Bug Fixes

• Fixed #289 - Binary imcompatibility with code that was compiled against previous Failsafe versions.

2.4.2

Improvements

• Added RetryPolicy.onRetryScheduled event handler.
• Added ExecutionEvent.getExecutionCount() and ExecutionContext.getExecutionCount(), which distinguishes between attempts which may have been rejected and completed executions.
• Added Failsafe.none to create a no-op FailsafeExecutor.
• Improved support for outer Timeouts with retries.
• Fixed #221 - Added support for FailsafeExecutor.with(Executor).
• Fixed #277 - Changed Timeout to use Failsafe's internal scheduler, so that user provided ExecutorService shutdowns do not interfere with timeouts.
• Fixed #266 - Propagate Future cancellation to supplied CompletionStage when using getStageAsync.

Bug Fixes

• Fixed #267 - Allow null fallback values to be passed through when using nested fallbacks.

2.4.1

Improvements

• Fixed #234 - An outer Timeout should cancel any inner retries.

API Changes

• Deprecated Timeout.withCancel(boolean) and Timeout.canCancel(). Timeouts always cancel any executions and inner retries.
• Added Timeout.withInterrupt(boolean) to take the place of withCancel.
• Added ExecutionEvent.getElapsedAttemptTime().

Commits

• e992fce [maven-release-plugin] prepare release failsafe-2.4.4
• 15d539c Fix Fallback.onFailedAttempt
• d057983 Added Automatic-Module-Name entry to the generated manifest file (#296)
• 34a38f6 Improve javadocs wrt FailurePolicy exception handling conditions
• ad163c1 Create maven.yml
• 2e37486 Be slightly more defensive when clearing the forkJoinPoolThread ref in Delega...
• 19dfd28 Update push-javadoc for the separate website repo
• 062b910 Update links for failsafe.dev domain
• c446fae Changed FailsafeExecutor.getAsyncExecution to accept an AsyncRunnable
• 9ae6438 Added result type params and unified result types
• 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 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)