antirez 2039f1a38a UNSUBSCRIBE and PUNSUBSCRIBE: always provide a reply. ... UNSUBSCRIBE and PUNSUBSCRIBE commands are designed to mass-unsubscribe the client respectively all the channels and patters if called without arguments. However when these functions are called without arguments, but there are no channels or patters we are subscribed to, the old behavior was to don't reply at all. This behavior is broken, as every command should always reply. Also it is possible that we are no longer subscribed to a channels but we are subscribed to patters or the other way around, and the client should be notified with the correct number of subscriptions. Also it is not pretty that sometimes we did not receive a reply at all in a redis-cli session from these commands, blocking redis-cli trying to read the reply. This fixes issue #714.		2013-01-21 19:02:26 +01:00
..
assets	fix typos in tests/assets/default.conf	2012-03-29 18:23:04 +08:00
helpers	Regression test for issue 417 (memory leak when replicating to DB with id >= 10)	2012-03-30 10:26:07 +02:00
integration	A reimplementation of blocking operation internals.	2012-09-17 10:26:46 +02:00
support	Test: fixed osx "leaks" support in test.	2012-12-03 12:06:38 +01:00
tmp	minor fixes to the new test suite, html doc updated	2010-05-14 18:48:33 +02:00
unit	UNSUBSCRIBE and PUNSUBSCRIBE: always provide a reply.	2013-01-21 19:02:26 +01:00
test_helper.tcl	Test: MULTI/EXEC tests moved into multi.tcl.	2012-11-22 10:32:12 +01:00