Skip to content

config: fix trace-region-flow displayed incorrectly (#7993) - #8146

Merged
ti-chi-bot[bot] merged 2 commits into
tikv:release-7.5from
ti-chi-bot:cherry-pick-7993-to-release-7.5
May 13, 2024
Merged

ti-chi-bot[bot] merged 2 commits into
tikv:release-7.5from
ti-chi-bot:cherry-pick-7993-to-release-7.5

Conversation

@ti-chi-bot

Copy link
Copy Markdown
Member

This is an automated cherry-pick of #7993

What problem does this PR solve?

Issue Number: Close #7917.

What is changed and how does it work?

Check List

Tests

  • Unit test
  • Manual test

After this PR:

mysql> show config where name like "%pd-server.trace-region-flow%";
Empty set (0.01 sec)

Release note

None.

Signed-off-by: Ryan Leung <rleungx@gmail.com>
@ti-chi-bot ti-chi-bot added release-note-none Denotes a PR that doesn't merit a release note. size/XS Denotes a PR that changes 0-9 lines, ignoring generated files. type/cherry-pick-for-release-7.5 This PR is cherry-picked to release-7.5 from a source PR. labels May 7, 2024
@ti-chi-bot

ti-chi-bot Bot commented May 7, 2024 •

Copy link
Copy Markdown
Contributor

[REVIEW NOTIFICATION]

This pull request has been approved by:

  • JmPotato

To complete the pull request process, please ask the reviewers in the list to review by filling /cc @reviewer in the comment.
After your PR has acquired the required number of LGTMs, you can assign this pull request to the committer in the list by filling /assign @committer in the comment to help you merge this pull request.

The full list of commands accepted by this bot can be found here.

Details

Reviewer can indicate their review by submitting an approval review.
Reviewer can cancel approval by submitting a request changes review.

@ti-chi-bot ti-chi-bot added the cherry-pick-approved Cherry pick PR approved by release team. label May 7, 2024
@ti-chi-bot
ti-chi-bot Bot requested review from JmPotato and rleungx May 7, 2024 05:51
Signed-off-by: Ryan Leung <rleungx@gmail.com>
@ti-chi-bot ti-chi-bot Bot added the status/LGT1 Indicates that a PR has LGTM 1. label May 11, 2024
@JmPotato JmPotato added the require-LGT1 Indicates that the PR requires an LGTM. label May 13, 2024
@JmPotato

Copy link
Copy Markdown
Member

/merge

@ti-chi-bot

ti-chi-bot Bot commented May 13, 2024

Copy link
Copy Markdown
Contributor

@JmPotato: It seems you want to merge this PR, I will help you trigger all the tests:

/run-all-tests

You only need to trigger /merge once, and if the CI test fails, you just re-trigger the test that failed and the bot will merge the PR for you after the CI passes.

If you have any questions about the PR merge process, please refer to pr process.

Details

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the ti-community-infra/tichi repository.

@ti-chi-bot

ti-chi-bot Bot commented May 13, 2024

Copy link
Copy Markdown
Contributor

This pull request has been accepted and is ready to merge.

DetailsCommit hash: 785b57f

@ti-chi-bot ti-chi-bot Bot added the status/can-merge Indicates a PR has been approved by a committer. label May 13, 2024
@ti-chi-bot
ti-chi-bot Bot merged commit 7eb188c into tikv:release-7.5 May 13, 2024
@JmPotato
JmPotato deleted the cherry-pick-7993-to-release-7.5 branch May 13, 2024 04:25
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

cherry-pick-approved Cherry pick PR approved by release team. release-note-none Denotes a PR that doesn't merit a release note. require-LGT1 Indicates that the PR requires an LGTM. size/XS Denotes a PR that changes 0-9 lines, ignoring generated files. status/can-merge Indicates a PR has been approved by a committer. status/LGT1 Indicates that a PR has LGTM 1. type/cherry-pick-for-release-7.5 This PR is cherry-picked to release-7.5 from a source PR.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants