Potential concurrency bug in logger
Open
Nobody has claimed this yet.
bug
- Dominant language
- Go
- Stars
- 73
- Forks
- 41
- Avg merge
- 21h 3m
- Merged PRs (30d)
- 21
Description
Bug Report
Please answer these questions before submitting your issue. Thanks!
1. Minimal reproduce step (Required)
Start TiProxy with TiUP cluster.
2. What did you expect to see? (Required)
Always print welcome info.
3. What did you see instead (Required)
Theoretically, there's possibility that the welcome info is printed before initializing the log file, so the welcome info may not be printed.
4. What is your version? (Required)
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 reviewing TiProxy startup and logger initialization when launched with TiUP cluster, then investigate whether welcome information can be emitted before the log file is ready. Reproduce the reported ordering if possible and verify that welcome information is always printed after the initialization change.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- backend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100