You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Error: subscriptions are active but got an invalid reply: OK
at RedisClient.return_reply (/usr/local/lib/node_modules/redis/index.js:417:19)
at RedisReplyParser. (/usr/local/lib/node_modules/redis/index.js:87:14)
at RedisReplyParser.emit (events.js:64:17)
at RedisReplyParser.send_reply (/usr/local/lib/node_modules/redis/lib/parser/javascript.js:266:18)
at RedisReplyParser.execute (/usr/local/lib/node_modules/redis/lib/parser/javascript.js:120:22)
at RedisClient.on_data (/usr/local/lib/node_modules/redis/index.js:328:27)
at Socket. (/usr/local/lib/node_modules/redis/index.js:99:14)
at Socket.emit (events.js:64:17)
at Socket._onReadable (net.js:672:14)
at IOWatcher.onReadable [as callback] (net.js:177:10)
Removing the call to quit fixes this, but I don't know if it destroys the socket.
The text was updated successfully, but these errors were encountered:
* connection error did not properly trigger reconnection logic [GH-85]
* client.hmget(key, [val1, val2]) was not expanding properly [GH-66]
* client.quit() while in pub/sub mode would throw an error [GH-87]
* client.multi(['hmset', 'key', {foo: 'bar'}]) fails [GH-92]
As discussed on IRC, when doing something like:
The client raises an exception:
Removing the call to
quit
fixes this, but I don't know if it destroys the socket.The text was updated successfully, but these errors were encountered: