-
Notifications
You must be signed in to change notification settings - Fork 287
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
precheck(dm): fix MySQL 8.0 SHOW GRANTS with role #6485
Conversation
Signed-off-by: lance6716 <lance6716@gmail.com>
[REVIEW NOTIFICATION] This pull request has been approved by:
To complete the pull request process, please ask the reviewers in the list to review by filling The full list of commands accepted by this bot can be found here. Reviewer can indicate their review by submitting an approval review. |
This comment was marked as resolved.
This comment was marked as resolved.
/check-issue-triage-complete |
Signed-off-by: lance6716 <lance6716@gmail.com>
/run-all-tests |
Signed-off-by: lance6716 <lance6716@gmail.com>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
Signed-off-by: lance6716 <lance6716@gmail.com>
Signed-off-by: lance6716 <lance6716@gmail.com>
/run-verify |
/cc @liuzix @hi-rustin some CDC schema storage snapshot behaviour is changed, please review |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
lgtm. But I don't really understand the changes under cdc/entry. Do they also relate to the compatibility issue of DM?
/run-dm-integration-test |
This pull request has been accepted and is ready to merge. Commit hash: 5a50980
|
/run-verify |
/run-dm-integration-test |
/hold |
source bound is not stable,will update it later |
/unhold /merge |
This pull request has been accepted and is ready to merge. Commit hash: f8dd73a
|
/run-all-tests |
/run-dm-integration-test |
/unhold |
@lance6716: Your PR was out of date, I have automatically updated it for you. At the same time I will also trigger all tests for you: /run-all-tests 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. 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. |
/run-leak-test |
/run-verify |
/run-kafka-integration-test |
1 similar comment
/run-kafka-integration-test |
Signed-off-by: lance6716 lance6716@gmail.com
What problem does this PR solve?
Issue Number: close #6448 close #6506
What is changed and how it works?
introduce pingcap/tidb#36565 to fix the issue , and also pingcap/tidb#36576 by the way
Check List
Tests
Questions
Will it cause performance regression or break compatibility?
Do you need to update user documentation, design documentation or monitoring documentation?
Release note