Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Data Race Issues on UnPatch

Open
#19 0 comments 0 reactions 0 assignees View on GitHub

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

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

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from foxcpp/go-mockdns

All issues in foxcpp/go-mockdns

Similar issues

More Go issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.