-
Notifications
You must be signed in to change notification settings - Fork 1.8k
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
Asynchronous PSUBSCRIBE command fails when using RESP3 #815
Comments
Thanks, I'll take a look. Actually I think We should probably do it but it will warrant discussion around whether it's out of scope for a "minimalist" Redis library. Edit: The bug also exists in $ redis-cli
127.0.0.1:6379> hello 3
1# "server" => "redis"
2# "version" => "999.999.999"
3# "proto" => (integer) 3
4# "id" => (integer) 5
5# "mode" => "standalone"
6# "role" => "master"
7# "modules" => (empty array)
127.0.0.1:6379> subscribe foo
Reading messages... (press Ctrl-C to quit)
Error: Protocol error, got ">" as reply type byte |
Turned out to be simpler than I thought. |
I've tested your branch in the project I'm working on and I confirm it fixes the issue. Thanks a lot! :) |
The following toy implementation shows how execution of asynchronous
PSUBSCRIBE
command using currentRESP3
support in master (i.e. #805 already merged) fails with errorProtocol error, got ">" as reply type byte
. This has been tested using Redis Server 6.0.3. Same logic using RESP2 works as expected.The text was updated successfully, but these errors were encountered: