Data Race Issues on UnPatch
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 35/100
- Issue type
- Bug
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- go
- Domain
- networking, testing-qa
Research direction
Start by locating the UnPatch implementation and its callers in the go-mockdns codebase, then run the relevant tests with the race detector if available. Determine how concurrent unpatching currently behaves; done means callers can synchronize UnPatch without triggering a data race.
Written by the indexing model from the issue text.
Description
It would be convenient fi there was a way to UnPatch the mock server without risking a race condition. There is no mutex available to sync the unpatch
- Dominant language
- Go
- Stars
- 49
- Forks
- 11
- PR merge metrics
- No merged PRs in 30d
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
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.
More from foxcpp/go-mockdns
-
Fallback on real DNSOpen
Difficulty 4/5 3-5 days Newbie friendliness 35/100
foxcpp/go-mockdns#18 · 1 comment ·
-
Difficulty 3/5 1-2 days Newbie friendliness 42/100
foxcpp/go-mockdns#7 ·
-
bug invalid
Difficulty 3/5 1-2 days Newbie friendliness 25/100
foxcpp/go-mockdns#5 · 5 comments ·
All issues in foxcpp/go-mockdns
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
duplication
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
openvibely/openvibely#1443 ·
Maintainers usually reply within 2 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 80/100
keyxmakerx/Chronicle#1179 ·
Maintainers usually reply within 1 day
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
michelangelo-ai/michelangelo#2258 ·
Maintainers usually reply within 1 day