Shut down subscriber read loop correctly#178
Open
nickstenning wants to merge 1 commit intor3labs:masterfrom
Open
Shut down subscriber read loop correctly#178nickstenning wants to merge 1 commit intor3labs:masterfrom
nickstenning wants to merge 1 commit intor3labs:masterfrom
Conversation
readLoop was leaking goroutines when subscribers were unsubscribed, because it was blocked trying to write a nil to erChan in response to an upstream io.EOF. This commit passes in a context to startReadLoop, ensuring that when that context is closed, the read loop terminates correctly. For SubscribeWithContext we just pass in the parent context, as there is no way to unsubscribe the handler. For SubscribeChanWithContext, we pass in a derived cancelable context, which we cancel explicitly when the channel is unsubscribed.
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
1 participant
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.
readLoop was leaking goroutines when subscribers were unsubscribed, because it was blocked trying to write a nil to erChan in response to an upstream io.EOF.
This commit passes in a context to startReadLoop, ensuring that when that context is closed, the read loop terminates correctly.
For SubscribeWithContext we just pass in the parent context, as there is no way to unsubscribe the handler.
For SubscribeChanWithContext, we pass in a derived cancelable context, which we cancel explicitly when the channel is unsubscribed.
For the maintainers: I'm not sure if this is the right fix for the underlying problem here. Very happy to go back and forth with you on what the correct fix actually is, and get this patch in shape.