-
Notifications
You must be signed in to change notification settings - Fork 128
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
Fix client side race condition #1124
Conversation
"go.uber.org/zap/zaptest" | ||
) | ||
|
||
func TestContext_RaceRegression(t *testing.T) { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Test taken from Groxx@1e5a037
Pull Request Test Coverage Report for Build a606b89c-de6f-41f7-a1d2-e8199e40e732
💛 - Coveralls |
9a50d70
to
a09a821
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yeah, with a minimal lock like that, it may be sufficient. Worth a try to reduce crashes while we fix the underlying cause.
What changed?
The problem is described here: #1117
That PR fixes leaking go routines but also introduces a race condition, this PR fixes the race.
Why?
How did you test it?
Output of the first test without the fix:
Potential risks