Handle peer disconnect in blocking calls #300
Merged
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.
Problem: Cancelled blocking call to XREADGROUP results in items put on PEL and inaccessible to other subscribers
Scenario:
Connection A writes items [XADD] in one goroutine
Connection B fetches items [XREADGROUP] from second goroutine - blocking
B is in the middle of a blocking call and is cancelled. Client disconnects as expected
Expected: Cancelled blocking call by B does not change the state of the stream and does not put items on PEL
Actual: blocking call proceeds and items are put on PEL
CC: @alicebob