context.Done() may never reach if waiting on r.incoming <- msgErr #936
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.
While analysing an issue, we observed that even after context is cancelled, the code was blocked in ConsumeClaim. And the reason is if the code if blocked at r.incoming <- msgErr, it may fail to honour or may skip the outside session.Context().Done().
Reference - https://stackoverflow.com/questions/67608032/context-ctx-done-not-being-executed-even-though-context-was-passed-to-the-functi
Solution is to add session.Context().Done() with r.incoming <- msgErr in select clause.