SOHU-Co / kafka-node / 716 / 11
89%
master: 89%

DEFAULT BRANCH: master
Ran
Files 53
Run time 3s
Badge
Embed ▾
README BADGES
x

If you need to use a raster PNG badge, change the '.svg' to '.png' in the link

Markdown

Textile

RDoc

HTML

Rst
coverage: 87.406%. Remained the same
KAFKA_VERSION=0.10

cron

travis-ci

Xiaoxin Lu 
<a href="https://github.com/SOHU-Co/kafka-node/commit/<a class=hub.com/SOHU-Co/kafka-node/commit/5f1ec838e2b3c8e6d34bc7f53b9d8e0c09673db2">5f1ec838e<a href="https://github.com/SOHU-Co/kafka-node/commit/5f1ec838e2b3c8e6d34bc7f53b9d8e0c09673db2">&quot;&gt;Fix Stale Commit Queue for ConsumerGroupStream (#891)

The commit at https://github.com/SOHU-Co/kafka-node/commit/</a><a class="double-link" href="https://github.com/SOHU-Co/kafka-node/commit/<a class="double-link" href="https://github.com/SOHU-Co/kafka-node/commit/abc160986765ebf94b121d56cadaa4a3d426559a">abc160986</a>">abc160986</a><a href="https://github.com/SOHU-Co/kafka-node/commit/5f1ec838e2b3c8e6d34bc7f53b9d8e0c09673db2"> introduced a bug
where the offset was incremented at the wrong location.

commitQueued then expected the offset committed to match what is currently in the queue, and that commit broke this.

This results in commit records never being correctly removed from the commitQueue, leading to
weird behavior when committing and messages being consumed twice when rebalances occur relating
to committing stale offsets.

1062 of 1429 branches covered (74.32%)

3380 of 3867 relevant lines covered (87.41%)

6953.78 hits per line

Source Files on job 716.11 (KAFKA_VERSION=0.10)