-
-
Notifications
You must be signed in to change notification settings - Fork 348
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
[bugfix] fix possible mutex lockup during streaming code #2633
[bugfix] fix possible mutex lockup during streaming code #2633
Conversation
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.
The storing a context on the Stream feels wrong. It's something the context package warns against doing and the Go team wrote a whole blog post about. We might have a good reason for it, but I don't know what the motivation for it is and why it has to be done this way.
have rearchitected with this now in mind :) |
99df0d5
to
b5719bd
Compare
just wanna make one last change, changing to draft until then even though all tests are passing |
…clude relevant stream type
Description
This fixes an issue I have noticed a few times on my own instance. It rewrites Stream{} to use much less mutex locking, and updates related code calling it.
Checklist
go fmt ./...
andgolangci-lint run
.