All Versions
53
Latest Version
Avg Release Cycle
87 days
Latest Release
-

Changelog History
Page 2

  • v2.4.4 Changes

    🐛 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.

  • v2.4.3 Changes

    🐛 Bug Fixes

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

  • v2.4.2 Changes

    👌 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.

  • v2.4.1 Changes

    👌 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().

  • v2.4.0 Changes

    👌 Improvements

    • ➕ Added time based thresholding support to CircuitBreaker via:
      • withFailureThreshold(int failureThreshold, Duration failureThresholdingPeriod)
      • withFailureThreshold(int failureThreshold, int failureExecutionThreshold, Duration failureThresholdingPeriod)
      • withFailureRateThreshold(int failureRateThreshold, int failureExecutionThreshold, Duration failureThresholdingPeriod)
    • ➕ Added getters to CircuitBreaker for existing count based thresholding settings:
      • getFailureThresholdingCapacity()
      • getSuccessThresholdingCapacity()
    • And added getters to CircuitBreaker for new time based thresholding settings:
      • getFailureRateThreshold()
      • getFailureExecutionThreshold()
      • getFailureThresholdingPeriod()
    • ➕ Added some new metrics to CircuitBreaker:
      • getSuccessRate()
      • getFailureRate()
      • getExecutionCount()

    API Changes

    • 🔄 Changed the return type of CircuitBreaker's getFailureThreshold() and getSuccessThreshold() from Ratio to int. getFailureThresholdingCapacity, getFailureRateThreshold, getFailureExecutionThreshold, and getSuccessThresholdingCapacity provide additional detail about thresholding configuration.
    • ✂ Removed support for the previously deprecated CircuitBreaker.withTimeout. The Timeout policy should be used instead.

  • v2.3.5 Changes

    🐛 Bug Fixes

    • 🛠 Fixed #242 - Delays not occurring between manually triggered async execution retries.

  • v2.3.4 Changes

    👌 Improvements

    • 👀 Re-worked internal threading to only create async threads immediately prior to supplier execution. See #230.

    🐛 Bug Fixes

    • 🛠 Fixed #240 - handleResult(null) always triggering when an exception is thrown.

  • v2.3.3 Changes

    February 10, 2020

    👌 Improvements

    ➕ Added support for CompletionStage to the Fallback policy.

    🐛 Bug Fixes

    • 🛠 Fixed #224 - Allow combining random delay and jitter.

    API Changes

    • 📦 Fallback.apply was made package private.
    • 📦 DelayablePolicy.computeDelay was made package private.

  • v2.3.2 Changes

    January 25, 2020

    👌 Improvements

    • ➕ Added CircuitBreaker.getRemainingDelay().
    • ➕ Added support for Fallback.VOID.

    🐛 Bug Fixes

    • 🛠 Fixed #216 - Incorrect computation of randomDelay.

  • v2.3.1 Changes

    August 22, 2019

    🐛 Bug Fixes

    • 🛠 Fixed #206 - Problem with Fallback converting from failure to success.

    👌 Improvements

    • ⏱ Set setRemoveOnCancelPolicy(true) for the internal delay scheduler.
    • ➕ Added Scheduler.DEFAULT to return the default scheduler Failsafe uses.