Check slice boundary when parsing packets
Open
Nobody has claimed this yet.
refactor
- Dominant language
- Go
- Stars
- 73
- Forks
- 41
- Avg merge
- 21h 3m
- Merged PRs (30d)
- 21
Description
Development Task
Most packet parsing in TiProxy doesn't check the boundaries and it may panic if the client sends a malformed packet. This is not good. We'd better check it.
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 locating the packet-parsing entry points in TiProxy and tracing where input slices are indexed. Check the relevant parser tests or add focused malformed-packet cases; done means malformed client packets are handled without slice-boundary panics across the parsing paths.
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
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100