Skip to content

repair(cdc): replay Kafka retry validation on live develop - #290

Merged
github-actions[bot] merged 3 commits into
developfrom
repair/cdc-kafka-retry-bounds-106add
Aug 11, 2026
Merged

repair(cdc): replay Kafka retry validation on live develop#290
github-actions[bot] merged 3 commits into
developfrom
repair/cdc-kafka-retry-bounds-106add

Conversation

@seonghobae

Copy link
Copy Markdown
Collaborator

Rebuilds the #250 / #251 retry-configuration fix directly from live protected develop@106add38465937f6eb4e4accc185fd30aab4446f because #251 no longer descends from the current protected tip. Keep Draft.

TDD restart:

  • exact base at branch creation: 106add38465937f6eb4e4accc185fd30aab4446f;
  • test-only RED head: 773634c2d4bbe94f3af4c7ac0ad67d07afa99b41;
  • production boundary under test: KafkaConfig.kafkaListenerErrorHandler(...);
  • fail-first assertions require negative retry backoff / retry attempts to be rejected with stable configuration-key diagnostics.

The old #251 production behavior is not yet copied into this replacement. First require hosted RED on this exact ancestry, then apply the smallest GREEN and prove preservation before closing #251. Shared coverage/scanner/literal-source/independent-review gates remain separate blockers and no prior-head evidence transfers.

@coderabbitai

coderabbitai Bot commented Aug 11, 2026

Copy link
Copy Markdown
Contributor

Warning

Review limit reached

@seonghobae, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 1 minute

You've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository.

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details
⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro Plus

Run ID: 5d64ac45-09da-47c2-b62e-01610d892356

📥 Commits

Reviewing files that changed from the base of the PR and between ae4efe6 and 13f64c5.

📒 Files selected for processing (2)
  • cdc-service/src/main/java/com/xtrmetl/cdc/config/KafkaConfig.java
  • cdc-service/src/test/java/com/xtrmetl/cdc/config/KafkaConfigTest.java

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands.

@seonghobae
seonghobae marked this pull request as ready for review August 11, 2026 22:17
@github-actions
github-actions Bot merged commit f62b025 into develop Aug 11, 2026
39 of 40 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant