This is an automated email from the ASF dual-hosted git repository.
github-bot pushed a change to branch regen_bot
in repository https://gitbox.apache.org/repos/asf/camel.git
discard 44d0a562917 Regen for commit cbe5c7ce6151fed406522c5f0d0391db18da70c0
add 33807af8f58 CAMEL-18020: fix a possible NPE due to uninitialized
consumer in poll exception strategies
add 6ccf9cc2723 (chores) camel-kafka: use final fields where possible
add 944e65b0ae2 (chores) camel-kafka: ensures all writes to the last error
happen through the setter
add dbde0cfdcbe Regen for commit 944e65b0ae245e157aa5df2405edaf57c918d63a
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 (44d0a562917)
\
N -- N -- N refs/heads/regen_bot (dbde0cfdcbe)
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:
.../camel/component/kafka/KafkaFetchRecords.java | 20 ++++++++++++--------
.../apache/camel/component/kafka/KafkaProducer.java | 4 ++--
.../consumer/errorhandler/KafkaErrorStrategies.java | 2 ++
.../errorhandler/ReconnectErrorStrategy.java | 2 +-
.../consumer/errorhandler/StopErrorStrategy.java | 2 +-
.../kafka/consumer/support/KafkaResumable.java | 2 +-
.../resume/kafka/AbstractKafkaResumeStrategy.java | 4 ++--
7 files changed, 21 insertions(+), 15 deletions(-)