Skip to content
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

Concurrent-safe notification mock #2578

Merged
merged 1 commit into from
Jan 17, 2017
Merged

Concurrent-safe notification mock #2578

merged 1 commit into from
Jan 17, 2017

Conversation

ybubnov
Copy link

@ybubnov ybubnov commented Dec 7, 2016

This patch provides additional attribute to the notification mock in
order to protect an access to the internal maps from multiple
go-routines. This is required to prevent panic errors caused by
inconsistent map state.

fixes #2269

This patch provides additional attribute to the notification mock in
order to protect an access to the internal maps from multiple
go-routines. This is required to prevent panic errors caused by
inconsistent map state.
@ybubnov
Copy link
Author

ybubnov commented Jan 5, 2017

Hi, sorry to being annoying but I don't know the process of merging pull requests, thus does this PR have any chance to be reviewed (do I have any mistakes in formatting the PR title or comments)? Or just, please, put any reasonable label to this PR to know it is not forgotten.

@slackpad slackpad added this to the 0.7.3 milestone Jan 5, 2017
@slackpad slackpad merged commit 25fb498 into hashicorp:master Jan 17, 2017
@slackpad
Copy link
Contributor

Thanks and sorry for the delay merging this one!

@ybubnov ybubnov deleted the concurrent-safe-notification-mock branch January 17, 2017 17:02
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Panic in TestCheckMonitor
2 participants