🐛(ZENKO-5346) remove duplicated word in ConsumerLagWarning description - #2492
🐛(ZENKO-5346) remove duplicated word in ConsumerLagWarning description#2492DarkIsDude wants to merge 3 commits into
Conversation
Hello darkisdude,My role is to assist you with the merge of this Available options
Available commands
Status report is not available. |
Incorrect fix versionThe
Considering where you are trying to merge, I ignored possible hotfix versions and I expected to find:
Please check the |
c3f19ed to
06f6216
Compare
![claude[bot]](https://avatars.githubusercontent.com/in/1236702?s=60&v=4){kind=small}
Request integration branchesWaiting for integration branch creation to be requested by the user. To request integration branches, please comment on this pull request with the following command: Alternatively, the |
|
probably not worth fixing in 2.11, won't ever be released I think : 2.14 or maybe 2.15 is likely enough... or even just fix on latest version, not very important. |
delthas
left a comment
delthas
left a comment
There was a problem hiding this comment.
Would have been a good candidate for Pod UI agent thing
|
/approve |
Integration data createdI have created the integration data for the additional destination branches.
The following branches will NOT be impacted:
You can set option The following options are set: approve |
Build failedThe build for commit did not succeed in branch bugfix/ZENKO-5346/fix-consumer-lag-alert-typo The following options are set: approve |
Build failedThe build for commit did not succeed in branch w/2.14/bugfix/ZENKO-5346/fix-consumer-lag-alert-typo The following options are set: approve |
Build failedThe build for commit did not succeed in branch w/2.12/bugfix/ZENKO-5346/fix-consumer-lag-alert-typo The following options are set: approve |
Build failedThe build for commit did not succeed in branch bugfix/ZENKO-5346/fix-consumer-lag-alert-typo The following options are set: approve |
21a76a2 to
a57e29b
Compare
History mismatchMerge commit #06f62161035cb21025e80ec5412f660e28d71a47 on the integration branch It is likely due to a rebase of the branch Please use the The following options are set: approve |
|
/reset |
Reset completeI have successfully deleted this pull request's integration branches. The following options are set: approve |
Integration data createdI have created the integration data for the additional destination branches.
The following branches will NOT be impacted:
You can set option The following options are set: approve |
Build failedThe build for commit did not succeed in branch w/2.14/bugfix/ZENKO-5346/fix-consumer-lag-alert-typo The following options are set: approve |
Build failedThe build for commit did not succeed in branch bugfix/ZENKO-5346/fix-consumer-lag-alert-typo The following options are set: approve |
Build failedThe build for commit did not succeed in branch w/2.15/bugfix/ZENKO-5346/fix-consumer-lag-alert-typo The following options are set: approve |
Build failedThe build for commit did not succeed in branch bugfix/ZENKO-5346/fix-consumer-lag-alert-typo The following options are set: approve |
Build failedThe build for commit did not succeed in branch w/2.15/bugfix/ZENKO-5346/fix-consumer-lag-alert-typo The following options are set: approve |
Build failedThe build for commit did not succeed in branch bugfix/ZENKO-5346/fix-consumer-lag-alert-typo The following options are set: approve |
|
/create_pull_requests |
Integration data createdI have created the integration data for the additional destination branches.
The following branches will NOT be impacted:
Follow integration pull requests if you would like to be notified of The following options are set: approve, create_pull_requests |
Build failedThe build for commit did not succeed in branch bugfix/ZENKO-5346/fix-consumer-lag-alert-typo The following options are set: approve, create_pull_requests |
The "Pause and resume archiving to azure (PutObject before pause)" scenario was commented out on 2.14+ by 553beb4 (ZENKO-5203) but never backported, so it still runs on 2.13 and fails nearly every run of ctst-end2end-sharded: the objects are put before the location is paused, so they have usually already transitioned by the time the pause applies. Issue: ZENKO-5346
ConflictA conflict has been raised during the update of Please resolve the conflict on the integration branch ( Here are the steps to resolve this conflict: git fetch
git checkout w/2.14/bugfix/ZENKO-5346/fix-consumer-lag-alert-typo
git pull # or "git reset --hard origin/w/2.14/bugfix/ZENKO-5346/fix-consumer-lag-alert-typo"
git merge origin/development/2.14
# <intense conflict resolution>
git commit
git merge origin/bugfix/ZENKO-5346/fix-consumer-lag-alert-typo
# <intense conflict resolution>
git commit
git push -u origin w/2.14/bugfix/ZENKO-5346/fix-consumer-lag-alert-typoThe following options are set: approve, create_pull_requests |
There was a problem hiding this comment.
Backport from more recent branches
Build failedThe build for commit did not succeed in branch bugfix/ZENKO-5346/fix-consumer-lag-alert-typo The following options are set: approve, create_pull_requests |
Build failedThe build for commit did not succeed in branch w/2.15/bugfix/ZENKO-5346/fix-consumer-lag-alert-typo The following options are set: approve, create_pull_requests |
Build failedThe build for commit did not succeed in branch w/2.14/bugfix/ZENKO-5346/fix-consumer-lag-alert-typo The following options are set: approve, create_pull_requests |
5 participants
What does this PR do, and why do we need it?
The
ConsumerLagWarningalert description inmonitoring/kafka/alerts.yamlread "has been more more than ... seconds". This text is rendered as-is in Prometheus/Alertmanager notifications, so the typo is user-visible. This removes the duplicated "more".Which issue does this PR fix?
Fixes ZENKO-5346.
Special notes for your reviewers:
Text-only change to an alert annotation — no rule expression, threshold, or label touched.