fix: 'fatal error: concurrent map read and map write' crash#144
Merged
sebastianrakel merged 1 commit intovoxpupuli:mainfrom Mar 17, 2026
Merged
fix: 'fatal error: concurrent map read and map write' crash#144sebastianrakel merged 1 commit intovoxpupuli:mainfrom
sebastianrakel merged 1 commit intovoxpupuli:mainfrom
Conversation
bootc
approved these changes
Mar 17, 2026
Contributor
|
Tested locally and works for me, thanks. |
sebastianrakel
approved these changes
Mar 17, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
GetConfig() was called on every HTTP request, meaning concurrent requests would all try to initialize Viper's config at the same time, causing a 'fatal error: concurrent map read and map write' crash.
Wrapped the initialization in sync.Once so it runs exactly once at startup and the result is cached for all subsequent calls, crashes no longer occurs.