Non-UTF8 Review
Open
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 138
- Forks
- 31
- PR merge metrics
- No merged PRs in 30d
Description
Ensure that cbft doesn't blow up when passed data that is not in UTF8 format.
Contributor guide
No contributing guide indexed for this repository
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
No file, test, or entry point is named. Start by finding where cbft accepts or decodes input and reproduce the failure with non-UTF8 data. Done means the behavior is covered by a regression test and cbft no longer blows up on that input.
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
- 35/100