This is an automated email from the ASF dual-hosted git repository.
github-bot pushed a change to branch regen_bot_3x
in repository https://gitbox.apache.org/repos/asf/camel.git
omit 2515ed1d54e Regen for commit 4204190ea96d3fe3a6914f81d83dd3600264fef8
add a0ae9942dee Regen for commit 4204190ea96d3fe3a6914f81d83dd3600264fef8
add 62bb0f75b5d (chores) camel-test-infra-kafka: do use Kafka 2.x when
requested
add aaf7cc6254a CAMEL-18985: Updated `SyncCommitManager` to perform
offsets auto-commit of the last `poll()` only if the auto-commit is enabled in
the configuration.
add 77d84b45e9d (chores) camel-kafka: only run certain Kafka 3 tests when
using a Kafka 3 container
add f6b7b6c2e27 Regen for commit 77d84b45e9d3f75212071a23caaf1d712095307f
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 (2515ed1d54e)
\
N -- N -- N refs/heads/regen_bot_3x (f6b7b6c2e27)
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/component/kafka/consumer/SyncCommitManager.java | 6 ++++--
.../camel/component/kafka/integration/KafkaConsumerAuthIT.java | 7 +++++++
.../component/kafka/integration/KafkaConsumerAuthInvalidIT.java | 7 +++++++
.../kafka/integration/KafkaConsumerAuthInvalidWithReconnectIT.java | 7 +++++++
.../test/infra/kafka/services/ContainerLocalKafkaService.java | 6 +++++-
.../camel/test/infra/kafka/services/KafkaServiceFactory.java | 4 ++--
6 files changed, 32 insertions(+), 5 deletions(-)
