1922
92%
main: 92%

Ran 18 May 2019 06:17PM UTC

Jobs 1

Files 25

Run time 2s

Badge

Embed ▾

Committed 18 May 2019 06:07PM UTC coverage: 92.062% (-0.03%) from 92.094%

Build # 1922

Build Type

push

travis-ci

Committed by

kozlovic

Commit Message

[FIXED] Clustering: channel first/last sequence may fall to zero

This could happen if the leader took a snapshot while messages were
not yet expired, then a node is started without state and tries
to restore from this snapshot. If the messages have expired by then,
no message would be stored. If that node later did a snapshot itself,
it would persist in it the first/last being zero. If no message are
published and this node becomes leader, it would start storing
messages at the wrong sequence and would also send the bad snapshot
to other nodes.

Resolves #833

Signed-off-by: Ivan Kozlovic <ivan@synadia.com>

Run Details

11505 of 12497 relevant lines covered (92.06%)

49165.99 hits per line

Jobs

ID	Job ID	Ran	Files	Coverage
2	1922.2	18 May 2019 06:17PM UTC	0	92.06	Travis Job 1922.2

Source Files on build 1922

Detailed source file information is not available for this build.

nats-io / nats-streaming-server / 1922
92%
main: 92%

README BADGES
x

Markdown

Textile

RDoc

HTML

Rst

Jobs

Source Files on build 1922

nats-io / nats-streaming-server / 1922 92% main: 92%

README BADGES x

Markdown

Textile

RDoc

HTML

Rst

Jobs

Source Files on build 1922

nats-io / nats-streaming-server / 1922
92%
main: 92%

README BADGES
x