Closed db-will closed 1 day ago
Hi @db-will. Thanks for your PR.
I'm waiting for a pingcap member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test
on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.
Once the patch is verified, the new status will be reflected by the ok-to-test
label.
I understand the commands that are listed here.
/ok-to-test
[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: GMHDBJD, lance6716
The full list of commands accepted by this bot can be found here.
The pull request process is described here
Attention: Patch coverage is 0%
with 2 lines
in your changes missing coverage. Please review.
Project coverage is 55.1466%. Comparing base (
f1f286a
) to head (f26e2c0
). Report is 1 commits behind head on master.
🚨 Try these New Features:
What problem does this PR solve?
Issue Number: close #11489
What is changed and how it works?
Redact query arguments in dm log when there is retryable error happen in dm syncer.
Have searched for arguments in dm source code to find if there are any missing part for redacting, this one seems like the last missing piece.
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
None