Avoid recoverable panic before handshake stage
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 73
- Forks
- 41
- Avg merge
- 21h 3m
- Merged PRs (30d)
- 21
Description
Development Task
Now TiProxy might report recoverable panic in many protocol related codes:
- For the packets before handshake.
- For the packets after handshake.
- For the packets from TiDB to client.
For this issue, I'm only going to fix the first class. Because: we can assume the TiDB always gives the correct format of packets (or there might be some incompability), and we might assume the client after logging in will always give a correct protocol.
For now, usually the recoverable panic is caused by the port scanning software on the internet.
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 tracing TiProxy's protocol-related packet handling for packets received before the handshake, focusing on paths that report recoverable panics. Confirm the relevant behavior with malformed or unexpected pre-handshake packets; done means those packets no longer produce recoverable panics while post-handshake and TiDB-to-client handling remain out of scope.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- networking
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100