-
Notifications
You must be signed in to change notification settings - Fork 74
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
subscribing to an empty set kills pubsub #102
Comments
To add a bit more color, these appear to be the situations in which a subscriber stops listening:
I've validated with redis-cli that the messages are getting pushed to client (via the return value of |
Here's an example that will demonstrate this nicely:
Results in:
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
This appears to be a bug, but I'll leave that to the public to decide.
When subscribing to nothing, the pubsub stops listening completely.
After the first statement,
subscriber.next_published()
will never hear another reply.This doesn't appear to be documented on Redis Subscribe so I'm assuming this is a bug?
The text was updated successfully, but these errors were encountered: