search

spring-cloud / spring-cloud-circuitbreaker

Spring Cloud Circuit Breaker API and Implementations
Apache License 2.0
335 stars 110 forks source link

Bump resilience4j.version from 1.3.1 to 1.6.1 #82

Closed dependabot-preview[bot] closed 3 years ago

dependabot-preview[bot] commented 4 years ago

Bumps resilience4j.version from 1.3.1 to 1.6.1. Updates resilience4j-circuitbreaker from 1.3.1 to 1.6.1

Release notes

Sourced from resilience4j-circuitbreaker's releases.

Release v1.6.0

Enhancements

  • RetryConfig.DEFAULT_MAX_ATTEMPTS should be public #1180
  • Circuitbreaker doesn't open when nested TimeLimiter throws TimeOutCancellationException #1123
  • Enhance Server Side Events /circuitbreaker/events #1076
  • CallNotPermittedException should contain circuit breaker name (and possibly other information) #1062
  • Retry: Exponential backoff with constant behaviour after certain time #1044
  • Respecting the clock set in the CircuitBreakerStateMachine for detecting slow calls #734

Bugs

  • Circuit breaker stuck in HALF_OPEN state #935
  • Circuit breaker global fallback seems to not work when annotated method has more than 1 parameter #1174
  • Timelimiter metrics not calculated when using resilince4j-kotlin #1168
  • Problem with registering metrics for more than one circuit breaker #1131
  • ConcurrentModificationException warning log while consuming events #1115
  • CircuitBreakerConfig.Builder.waitDurationInOpenState() false documentation of when the function throws exception #1092

Release v1.5.0

  • Issue #855: Updated resilience4j-spring-boot2 to 2.3.0.RELEASE
  • Issue #855: Updated resilience4j-spring-cloud2 to 2.2.2.RELEASE
  • Issue #942: Introduced new CB metric "notPermittedCalls"
  • Issue #964: Added Kotlin DSL for building *Config and *Registry classes
  • Issue #979: Added fairCallHandlingEnabled flag to BulkheadConfig which controls whether FairSync or NonfairSync should be used in the Semaphore.
  • Issue #982: Added support to configure exponential random backoff via Spring config
  • Issue #991: Fixed bug that auto transition to half_open happens even if the state is forced open.
  • Issue #1000: Added toString to CircuitBreakerConfig
  • Issue #1003: Fixed bug that CircuitBreaker tries to obtain permission twice in circuitBreaker.decorateEitherSupplier()

Release v1.4.0

  • Issue #703: Add a feature that allows to plug-in your own Registry implementation which can be based on a cache library if needed.
  • Issue #737: Updated reactor version to 3.3.0.RELEASE
  • Issue #933: Add RegistryStore and builder methods to create BulkheadRegistry and ThreadPoolBulkheadRegistry
  • Issue #924: Add RegistryStore and builder methods to create RetryRegistry
  • Issue #910: Add RegistryStore and builder methods to create RateLimiterRegistry
  • Issue #928: Fix TimeLimiter does not set a message for TimeoutException
  • Issue #916: Allow setting Retry Wait Duration Limit to value equal >= zero
  • Issue #887: Fixing Spring Boot Common and Spring Boot 2 modules share the same packages which is not allowed in the Java Module system
  • Issue #886: Add support for RxJava 3
  • Issue #913: Add proper graceful cleanup of resilience4j thread pool executors which make it properly cleaned on spring boot applications
  • Issue #939: Fix actuator shows Whitelabel error page with "Invalid Event"
  • Issue #958: Added missing method to set contextProgagators in ThreadPoolBulkheadConfigurationProperties
  • PR #914: Adding non-coroutine kotlin wrapper functions as a convenience
  • PR #943: Removed deprecated documentation
Changelog

Sourced from resilience4j-circuitbreaker's changelog.

= Release Notes

== Version 0.1.0

  • Initial version

=== Version 0.1.1

  • Added the functionality to add exceptions with are ignored by the CircuitBreaker

=== Version 0.1.2

  • Added the feature to get Metrics for function executions

=== Version 0.1.3

  • Added a static factory method for the CircuitBreakerConfig builder

=== Version 0.1.4

  • Added the feature to retry a failed function

=== Version 0.1.5

  • Added builders to simplify chaining of decorators

=== Version 0.1.6

  • Renamed project to javaslang-circuitbreaker

=== Version 0.1.7

  • Fixed Issue #2
  • Issue #3 Added a listener mechanism for state transitions

== Version 0.2.0

  • Removed Dropwizard Metrics, because its a too heavy dependency for such a lightweight library.
  • Changed the way exceptions can be handled. You have to provide a Predicate now instead of a list of exceptions to ignore.

== Version 0.3.0

  • The CircuitBreaker is based on a Ring Bit Buffer and a failure rate now.

=== Version 0.3.1

  • Changed the visibility of CircuitBreakerUtils.isCallPermitted to public.

=== Version 0.3.2

  • CircuitBreakerRegistry has a new method which takes a Supplier of a CircuitBreakerConfig so that the CircuitBreakerConfig is only created when needed.

=== Version 0.3.3

  • CircuitBreaker has a new method getCircuitBreakerConfig which allows to retrieve the CircuitBreakerConfig of the CircuitBreaker.
  • Renamed the state HALF_CLOSED to HALF_OPEN to match the pattern description of Martin Fowler.

=== Version 0.3.4

  • Added a Metrics interface to the CircuitBreaker which allows to retrieve current statistics like failureRate and number of buffer calls.

== Version 0.4.0

  • Updated javaslang from 2.0.0-RC4 to 2.0.1
Commits


Updates resilience4j-timelimiter from 1.3.1 to 1.6.1

Release notes

Sourced from resilience4j-timelimiter's releases.

Release v1.6.0

Enhancements

  • RetryConfig.DEFAULT_MAX_ATTEMPTS should be public #1180
  • Circuitbreaker doesn't open when nested TimeLimiter throws TimeOutCancellationException #1123
  • Enhance Server Side Events /circuitbreaker/events #1076
  • CallNotPermittedException should contain circuit breaker name (and possibly other information) #1062
  • Retry: Exponential backoff with constant behaviour after certain time #1044
  • Respecting the clock set in the CircuitBreakerStateMachine for detecting slow calls #734

Bugs

  • Circuit breaker stuck in HALF_OPEN state #935
  • Circuit breaker global fallback seems to not work when annotated method has more than 1 parameter #1174
  • Timelimiter metrics not calculated when using resilince4j-kotlin #1168
  • Problem with registering metrics for more than one circuit breaker #1131
  • ConcurrentModificationException warning log while consuming events #1115
  • CircuitBreakerConfig.Builder.waitDurationInOpenState() false documentation of when the function throws exception #1092

Release v1.5.0

  • Issue #855: Updated resilience4j-spring-boot2 to 2.3.0.RELEASE
  • Issue #855: Updated resilience4j-spring-cloud2 to 2.2.2.RELEASE
  • Issue #942: Introduced new CB metric "notPermittedCalls"
  • Issue #964: Added Kotlin DSL for building *Config and *Registry classes
  • Issue #979: Added fairCallHandlingEnabled flag to BulkheadConfig which controls whether FairSync or NonfairSync should be used in the Semaphore.
  • Issue #982: Added support to configure exponential random backoff via Spring config
  • Issue #991: Fixed bug that auto transition to half_open happens even if the state is forced open.
  • Issue #1000: Added toString to CircuitBreakerConfig
  • Issue #1003: Fixed bug that CircuitBreaker tries to obtain permission twice in circuitBreaker.decorateEitherSupplier()

Release v1.4.0

  • Issue #703: Add a feature that allows to plug-in your own Registry implementation which can be based on a cache library if needed.
  • Issue #737: Updated reactor version to 3.3.0.RELEASE
  • Issue #933: Add RegistryStore and builder methods to create BulkheadRegistry and ThreadPoolBulkheadRegistry
  • Issue #924: Add RegistryStore and builder methods to create RetryRegistry
  • Issue #910: Add RegistryStore and builder methods to create RateLimiterRegistry
  • Issue #928: Fix TimeLimiter does not set a message for TimeoutException
  • Issue #916: Allow setting Retry Wait Duration Limit to value equal >= zero
  • Issue #887: Fixing Spring Boot Common and Spring Boot 2 modules share the same packages which is not allowed in the Java Module system
  • Issue #886: Add support for RxJava 3
  • Issue #913: Add proper graceful cleanup of resilience4j thread pool executors which make it properly cleaned on spring boot applications
  • Issue #939: Fix actuator shows Whitelabel error page with "Invalid Event"
  • Issue #958: Added missing method to set contextProgagators in ThreadPoolBulkheadConfigurationProperties
  • PR #914: Adding non-coroutine kotlin wrapper functions as a convenience
  • PR #943: Removed deprecated documentation
Changelog

Sourced from resilience4j-timelimiter's changelog.

= Release Notes

== Version 0.1.0

  • Initial version

=== Version 0.1.1

  • Added the functionality to add exceptions with are ignored by the CircuitBreaker

=== Version 0.1.2

  • Added the feature to get Metrics for function executions

=== Version 0.1.3

  • Added a static factory method for the CircuitBreakerConfig builder

=== Version 0.1.4

  • Added the feature to retry a failed function

=== Version 0.1.5

  • Added builders to simplify chaining of decorators

=== Version 0.1.6

  • Renamed project to javaslang-circuitbreaker

=== Version 0.1.7

  • Fixed Issue #2
  • Issue #3 Added a listener mechanism for state transitions

== Version 0.2.0

  • Removed Dropwizard Metrics, because its a too heavy dependency for such a lightweight library.
  • Changed the way exceptions can be handled. You have to provide a Predicate now instead of a list of exceptions to ignore.

== Version 0.3.0

  • The CircuitBreaker is based on a Ring Bit Buffer and a failure rate now.

=== Version 0.3.1

  • Changed the visibility of CircuitBreakerUtils.isCallPermitted to public.

=== Version 0.3.2

  • CircuitBreakerRegistry has a new method which takes a Supplier of a CircuitBreakerConfig so that the CircuitBreakerConfig is only created when needed.

=== Version 0.3.3

  • CircuitBreaker has a new method getCircuitBreakerConfig which allows to retrieve the CircuitBreakerConfig of the CircuitBreaker.
  • Renamed the state HALF_CLOSED to HALF_OPEN to match the pattern description of Martin Fowler.

=== Version 0.3.4

  • Added a Metrics interface to the CircuitBreaker which allows to retrieve current statistics like failureRate and number of buffer calls.

== Version 0.4.0

  • Updated javaslang from 2.0.0-RC4 to 2.0.1
Commits


Updates resilience4j-reactor from 1.3.1 to 1.6.1

Release notes

Sourced from resilience4j-reactor's releases.

Release v1.6.0

Enhancements

  • RetryConfig.DEFAULT_MAX_ATTEMPTS should be public #1180
  • Circuitbreaker doesn't open when nested TimeLimiter throws TimeOutCancellationException #1123
  • Enhance Server Side Events /circuitbreaker/events #1076
  • CallNotPermittedException should contain circuit breaker name (and possibly other information) #1062
  • Retry: Exponential backoff with constant behaviour after certain time #1044
  • Respecting the clock set in the CircuitBreakerStateMachine for detecting slow calls #734

Bugs

  • Circuit breaker stuck in HALF_OPEN state #935
  • Circuit breaker global fallback seems to not work when annotated method has more than 1 parameter #1174
  • Timelimiter metrics not calculated when using resilince4j-kotlin #1168
  • Problem with registering metrics for more than one circuit breaker #1131
  • ConcurrentModificationException warning log while consuming events #1115
  • CircuitBreakerConfig.Builder.waitDurationInOpenState() false documentation of when the function throws exception #1092

Release v1.5.0

  • Issue #855: Updated resilience4j-spring-boot2 to 2.3.0.RELEASE
  • Issue #855: Updated resilience4j-spring-cloud2 to 2.2.2.RELEASE
  • Issue #942: Introduced new CB metric "notPermittedCalls"
  • Issue #964: Added Kotlin DSL for building *Config and *Registry classes
  • Issue #979: Added fairCallHandlingEnabled flag to BulkheadConfig which controls whether FairSync or NonfairSync should be used in the Semaphore.
  • Issue #982: Added support to configure exponential random backoff via Spring config
  • Issue #991: Fixed bug that auto transition to half_open happens even if the state is forced open.
  • Issue #1000: Added toString to CircuitBreakerConfig
  • Issue #1003: Fixed bug that CircuitBreaker tries to obtain permission twice in circuitBreaker.decorateEitherSupplier()

Release v1.4.0

  • Issue #703: Add a feature that allows to plug-in your own Registry implementation which can be based on a cache library if needed.
  • Issue #737: Updated reactor version to 3.3.0.RELEASE
  • Issue #933: Add RegistryStore and builder methods to create BulkheadRegistry and ThreadPoolBulkheadRegistry
  • Issue #924: Add RegistryStore and builder methods to create RetryRegistry
  • Issue #910: Add RegistryStore and builder methods to create RateLimiterRegistry
  • Issue #928: Fix TimeLimiter does not set a message for TimeoutException
  • Issue #916: Allow setting Retry Wait Duration Limit to value equal >= zero
  • Issue #887: Fixing Spring Boot Common and Spring Boot 2 modules share the same packages which is not allowed in the Java Module system
  • Issue #886: Add support for RxJava 3
  • Issue #913: Add proper graceful cleanup of resilience4j thread pool executors which make it properly cleaned on spring boot applications
  • Issue #939: Fix actuator shows Whitelabel error page with "Invalid Event"
  • Issue #958: Added missing method to set contextProgagators in ThreadPoolBulkheadConfigurationProperties
  • PR #914: Adding non-coroutine kotlin wrapper functions as a convenience
  • PR #943: Removed deprecated documentation
Changelog

Sourced from resilience4j-reactor's changelog.

= Release Notes

== Version 0.1.0

  • Initial version

=== Version 0.1.1

  • Added the functionality to add exceptions with are ignored by the CircuitBreaker

=== Version 0.1.2

  • Added the feature to get Metrics for function executions

=== Version 0.1.3

  • Added a static factory method for the CircuitBreakerConfig builder

=== Version 0.1.4

  • Added the feature to retry a failed function

=== Version 0.1.5

  • Added builders to simplify chaining of decorators

=== Version 0.1.6

  • Renamed project to javaslang-circuitbreaker

=== Version 0.1.7

  • Fixed Issue #2
  • Issue #3 Added a listener mechanism for state transitions

== Version 0.2.0

  • Removed Dropwizard Metrics, because its a too heavy dependency for such a lightweight library.
  • Changed the way exceptions can be handled. You have to provide a Predicate now instead of a list of exceptions to ignore.

== Version 0.3.0

  • The CircuitBreaker is based on a Ring Bit Buffer and a failure rate now.

=== Version 0.3.1

  • Changed the visibility of CircuitBreakerUtils.isCallPermitted to public.

=== Version 0.3.2

  • CircuitBreakerRegistry has a new method which takes a Supplier of a CircuitBreakerConfig so that the CircuitBreakerConfig is only created when needed.

=== Version 0.3.3

  • CircuitBreaker has a new method getCircuitBreakerConfig which allows to retrieve the CircuitBreakerConfig of the CircuitBreaker.
  • Renamed the state HALF_CLOSED to HALF_OPEN to match the pattern description of Martin Fowler.

=== Version 0.3.4

  • Added a Metrics interface to the CircuitBreaker which allows to retrieve current statistics like failureRate and number of buffer calls.

== Version 0.4.0

  • Updated javaslang from 2.0.0-RC4 to 2.0.1
Commits


Updates resilience4j-micrometer from 1.3.1 to 1.6.1

Release notes

Sourced from resilience4j-micrometer's releases.

Release v1.6.0

Enhancements

  • RetryConfig.DEFAULT_MAX_ATTEMPTS should be public #1180
  • Circuitbreaker doesn't open when nested TimeLimiter throws TimeOutCancellationException #1123
  • Enhance Server Side Events /circuitbreaker/events #1076
  • CallNotPermittedException should contain circuit breaker name (and possibly other information) #1062
  • Retry: Exponential backoff with constant behaviour after certain time #1044
  • Respecting the clock set in the CircuitBreakerStateMachine for detecting slow calls #734

Bugs

  • Circuit breaker stuck in HALF_OPEN state #935
  • Circuit breaker global fallback seems to not work when annotated method has more than 1 parameter #1174
  • Timelimiter metrics not calculated when using resilince4j-kotlin #1168
  • Problem with registering metrics for more than one circuit breaker #1131
  • ConcurrentModificationException warning log while consuming events #1115
  • CircuitBreakerConfig.Builder.waitDurationInOpenState() false documentation of when the function throws exception #1092

Release v1.5.0

  • Issue #855: Updated resilience4j-spring-boot2 to 2.3.0.RELEASE
  • Issue #855: Updated resilience4j-spring-cloud2 to 2.2.2.RELEASE
  • Issue #942: Introduced new CB metric "notPermittedCalls"
  • Issue #964: Added Kotlin DSL for building *Config and *Registry classes
  • Issue #979: Added fairCallHandlingEnabled flag to BulkheadConfig which controls whether FairSync or NonfairSync should be used in the Semaphore.
  • Issue #982: Added support to configure exponential random backoff via Spring config
  • Issue #991: Fixed bug that auto transition to half_open happens even if the state is forced open.
  • Issue #1000: Added toString to CircuitBreakerConfig
  • Issue #1003: Fixed bug that CircuitBreaker tries to obtain permission twice in circuitBreaker.decorateEitherSupplier()

Release v1.4.0

  • Issue #703: Add a feature that allows to plug-in your own Registry implementation which can be based on a cache library if needed.
  • Issue #737: Updated reactor version to 3.3.0.RELEASE
  • Issue #933: Add RegistryStore and builder methods to create BulkheadRegistry and ThreadPoolBulkheadRegistry
  • Issue #924: Add RegistryStore and builder methods to create RetryRegistry
  • Issue #910: Add RegistryStore and builder methods to create RateLimiterRegistry
  • Issue #928: Fix TimeLimiter does not set a message for TimeoutException
  • Issue #916: Allow setting Retry Wait Duration Limit to value equal >= zero
  • Issue #887: Fixing Spring Boot Common and Spring Boot 2 modules share the same packages which is not allowed in the Java Module system
  • Issue #886: Add support for RxJava 3
  • Issue #913: Add proper graceful cleanup of resilience4j thread pool executors which make it properly cleaned on spring boot applications
  • Issue #939: Fix actuator shows Whitelabel error page with "Invalid Event"
  • Issue #958: Added missing method to set contextProgagators in ThreadPoolBulkheadConfigurationProperties
  • PR #914: Adding non-coroutine kotlin wrapper functions as a convenience
  • PR #943: Removed deprecated documentation
Changelog

Sourced from resilience4j-micrometer's changelog.

= Release Notes

== Version 0.1.0

  • Initial version

=== Version 0.1.1

  • Added the functionality to add exceptions with are ignored by the CircuitBreaker

=== Version 0.1.2

  • Added the feature to get Metrics for function executions

=== Version 0.1.3

  • Added a static factory method for the CircuitBreakerConfig builder

=== Version 0.1.4

  • Added the feature to retry a failed function

=== Version 0.1.5

  • Added builders to simplify chaining of decorators

=== Version 0.1.6

  • Renamed project to javaslang-circuitbreaker

=== Version 0.1.7

  • Fixed Issue #2
  • Issue #3 Added a listener mechanism for state transitions

== Version 0.2.0

  • Removed Dropwizard Metrics, because its a too heavy dependency for such a lightweight library.
  • Changed the way exceptions can be handled. You have to provide a Predicate now instead of a list of exceptions to ignore.

== Version 0.3.0

  • The CircuitBreaker is based on a Ring Bit Buffer and a failure rate now.

=== Version 0.3.1

  • Changed the visibility of CircuitBreakerUtils.isCallPermitted to public.

=== Version 0.3.2

  • CircuitBreakerRegistry has a new method which takes a Supplier of a CircuitBreakerConfig so that the CircuitBreakerConfig is only created when needed.

=== Version 0.3.3

  • CircuitBreaker has a new method getCircuitBreakerConfig which allows to retrieve the CircuitBreakerConfig of the CircuitBreaker.
  • Renamed the state HALF_CLOSED to HALF_OPEN to match the pattern description of Martin Fowler.

=== Version 0.3.4

  • Added a Metrics interface to the CircuitBreaker which allows to retrieve current statistics like failureRate and number of buffer calls.

== Version 0.4.0

  • Updated javaslang from 2.0.0-RC4 to 2.0.1
Commits


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) - `@dependabot use these labels` will set the current labels as the default for future PRs for this repo and language - `@dependabot use these reviewers` will set the current reviewers as the default for future PRs for this repo and language - `@dependabot use these assignees` will set the current assignees as the default for future PRs for this repo and language - `@dependabot use this milestone` will set the current milestone as the default for future PRs for this repo and language - `@dependabot badge me` will comment on this PR with code to add a "Dependabot enabled" badge to your readme Additionally, you can set the following in your Dependabot [dashboard](https://app.dependabot.com): - Update frequency (including time of day and day of week) - Pull request limits (per update run and/or open at any time) - Out-of-range updates (receive only lockfile updates, if desired) - Security updates (receive only security updates, if desired)
codecov[bot] commented 4 years ago

Codecov Report

Merging #82 into master will not change coverage. The diff coverage is n/a.

Impacted file tree graph

@@            Coverage Diff            @@
##             master      #82   +/-   ##
=========================================
  Coverage     88.61%   88.61%           
  Complexity       52       52           
=========================================
  Files            11       11           
  Lines           202      202           
  Branches          4        4           
=========================================
  Hits            179      179           
  Misses           18       18           
  Partials          5        5

Continue to review full report at Codecov.

Legend - Click here to learn more Δ = absolute <relative> (impact), ø = not affected, ? = missing data Powered by Codecov. Last update d605312...df6ae97. Read the comment docs.