Make registration thread safe #96
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Issue
In my day job, we utilize
goworkerin a way such that workers are created programatically on the fly (supporting an event bus between different parts of our platform), not just in aninitfunction (as shown in quick start guide. Several of these are generated as part of a common initialization called from:main.goPeriodically, we observe a
fatal error: concurrent map writeserror in our automated test suite. We traced it down to the globalworkersmap and unprotectedRegisterfunction inworkers.go, and the fact that Go tests are executed in Goroutines. We permit Go's default behavior of running tests from different packages in parallel, and had to introduce a mutex to the section of our code booting go workers.log output from new test showing the problem using Go's race detector
Proposal
Use a mutex to restrict access to workers.