Daniel Shmuglin

Also experiencing failures during `commitOffset` when there're connection issues. The cause error is `RebalanceInProgress`, however a few moments before that I do see connectivity issues as well: ``` 2018-04-01T11:32:01.979Z ERROR...

@oleksiyk Since you have [disabled](https://github.com/oleksiyk/kafka/commit/ca70de0cc749b3bb40ed24b6f91e5db162fe5dbe) stack traces, I had to wrap the original error with my custom exception just to understand what's going on there. This is the nested error...

I'm pretty sure it **is** rejected :) I just don't understand whether there's anything special I need to do about it (since my handler returns that promise, I'd expect `no-kafka`...

I think I saw somewhere three retries. But then how should I handle those? According to [API](https://github.com/oleksiyk/kafka#groupconsumer-new-unified-consumer-api) my handler has to return `commitOffsets` result.

@oleksiyk then how come I get unhandled rejections? I guess there's some kind of state machine in your lib, according to kafka protocol. Might there be a chanсe that at...

I'll try to run your tests later this week and update. 10x

**UPD:** tried running my app (which uses no-kafka extensively) against kafka_2.11_1.0.0 - all my tests are green.

I'm also getting ``` TypeError: Cannot read property 'resolve' of undefined at Connection._receive (/app/node_modules/wix-bootstrap-greynode/node_modules/greynode-core/node_modules/no-kafka/lib/connection.js:205:30) at emitOne (events.js:96:13) at Socket.emit (events.js:188:7) at readableAddChunk (_stream_readable.js:176:18) at Socket.Readable.push (_stream_readable.js:134:10) at TCP.onread (net.js:547:20) ```...

same one

Once all instances had joined (deployed), looks like errors stop to appear. Still examining ...