2
92%
master: 92%

Ran 31 Jan 2015 05:04AM UTC

Files 117

Run time 48s

Badge

Embed ▾

Committed 31 Jan 2015 05:01AM UTC coverage: 96.294% (+0.08%) from 96.214%

Job # 134.2

Build Type

Pull #27

travis-ci

Committed by

kichik

Commit Message

Fix channel loss on reconnect
The scenario requires two or more close-by disconnections
1. Connect to Redis
2. Subscribe successfully to a channel
3. Forcibly kill the connection (by taking down Redis for example)
4. Let lettuce reconnect successfully
5. Forcibly kill the connection again right before activate() successfully subscribes
6. Let lettuce reconnect successfully
7. RedisPubSubConnectionImpl.channels is empty and the channel will stay unsubscribed

There doesn't seem to be a reason to clear out channels and patterns.
It is only used for persistence over different connections.
There is no downside to having a channel in that set even if the subscription was not successful.

Pull Request Pull Request #27: Fix channel loss on reconnect

Coverage Stats

3508 of 3643 relevant lines covered (96.29%)

0.96 hits per line

mp911de / lettuce / 134 / 2
92%
master: 92%

README BADGES
x

Markdown

Textile

RDoc

HTML

Rst

Source Files on job 134.2

mp911de / lettuce / 134 / 2 92% master: 92%

README BADGES x

Markdown

Textile

RDoc

HTML

Rst

Source Files on job 134.2

mp911de / lettuce / 134 / 2
92%
master: 92%

README BADGES
x