-
Notifications
You must be signed in to change notification settings - Fork 325
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
Closed reader does not return in Next #1218
Comments
A simple fix would be to add a case to the select to return when the consumer |
Thanks for reporting this.
Yes. I think this should be correct behavior. |
1 task
Thanks @RobertIndie , I've opened #1219 for a potential fix. |
RobertIndie
pushed a commit
that referenced
this issue
May 20, 2024
Fixes #1218 ### Motivation Calling Next on a reader already closed will block forever unless the context is canceled. Similarly, the call will not return if a different go routine closes the reader. ### Modifications Next now listens for the close channel of the consumer to return an error when it closes. Signed-off-by: Gaylor Bosson <gb@taurusgroup.ch>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Expected behavior
After closing a reader, I would expect the
Next
function to return an error that the reader is closed.Actual behavior
It blocks forever.
Steps to reproduce
Close the reader then call the
Next
, it will not return:System configuration
Pulsar version: v3.0
Pulsar client: v12.1
The text was updated successfully, but these errors were encountered: