-
Notifications
You must be signed in to change notification settings - Fork 2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Use of insensitiviesMaps in UnmarshalKey causes data race #353
Comments
I can confirm that. |
@dolanor fabric-sdk-go has fixed this issue, it doesn't use viper.UnmarshalKey anymore. |
@sudeshrshetty what does it use now? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The changes introduced in this commit cause a data race if UnmarshalKey is used in conjunction with other viper read functions such as GetString. If multiple goroutines are using combinations of UnmarshalKey and GetString (or other Get* functions) it causes panics.
The text was updated successfully, but these errors were encountered: