unstable test log_redaction
Open
Nobody has claimed this yet.
type/bug
- Dominant language
- Go
- Stars
- 56
- Forks
- 63
- Avg merge
- 2d 20h
- Merged PRs (30d)
- 34
Description
What did you do?
run integration test log_redaction
What did you expect to see?
No response
What did you see instead?
✓ VALIDATED: MySQL Query redacted to '?'
✗ FAILED: MySQL Args redacted to '?' placeholders - pattern not found: Args:.*\?
Debug: searching log content...
Versions of the cluster
Upstream TiDB cluster version (execute SELECT tidb_version(); in a MySQL client):
(paste TiDB cluster version here)
Upstream TiKV version (execute tikv-server --version):
(paste TiKV version here)
TiCDC version (execute cdc version):
master
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by running the integration test named log_redaction and inspect the log output around the failed MySQL Args redaction check. Trace the test's redaction and log-matching setup; done means the test reliably finds '?' placeholders for MySQL arguments without intermittent failures.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- testing-qa
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100