This is an automated email from the ASF dual-hosted git repository.
davsclaus pushed a change to branch feature/CAMEL-24819-circuit-breaker-counters
in repository https://gitbox.apache.org/repos/asf/camel.git
discard 4a0c892a785b Regen
discard f295885db85b CAMEL-24819: TUI help page explains how to read the
circuit breaker counters
discard d19b1b1eb136 CAMEL-24819: count fallback, timed out and bulkhead
rejected circuit breaker calls
add 09cfefceef40 CAMEL-24818: Address review feedback
add fc930e119fbe CAMEL-24818: name the version in the upgrade guide note
add a0421bb2740b CAMEL-24819: count fallback, timed out and bulkhead
rejected circuit breaker calls
add fb889a8884b6 CAMEL-24819: TUI help page explains how to read the
circuit breaker counters
This update added new revisions after undoing existing revisions.
That is to say, some revisions that were in the old version of the
branch are not in the new version. This situation occurs
when a user --force pushes a change and generates a repository
containing something like this:
* -- * -- B -- O -- O -- O (4a0c892a785b)
\
N -- N -- N
refs/heads/feature/CAMEL-24819-circuit-breaker-counters (fb889a8884b6)
You should already have received notification emails for all of the O
revisions, and so the following emails describe only the N revisions
from the common base, B.
Any revisions marked "omit" are not gone; other references still
refer to them. Any revisions marked "discard" are gone forever.
No new revisions were added by this update.
Summary of changes:
.../apache/camel/catalog/dev-consoles-openapi.json | 32 +---------------------
.../catalog/dev-consoles/fault-tolerance.json | 17 +-----------
.../camel/catalog/dev-consoles/resilience4j.json | 15 ----------
...eranceOpenWithFallbackExchangePropertyTest.java | 1 +
.../ROOT/pages/camel-4x-upgrade-guide-4_23.adoc | 9 ++++++
5 files changed, 12 insertions(+), 62 deletions(-)
