Dominic Evans

Yes this is a bug. ~I believe the issue will be that the producer dispatcher func simply iterates over the `Input` channel blocking until new messages are put on the...

@mbarbon thanks for this bug report, is your network partition drill easy for you to re-run? It would be great if you could test the latest release of Sarama (v1.33.0)...

@pavius thanks for this excellent write up. For some reason I hadn't been aware of this issue until I stumbled upon it just now. I've been browsing over your changes...

This error is because Sarama is tracking against supported versions of the Go toolchain + library (1.16.x+1.17.x) and so we've applied the changes necessary for the deprecation of ioutil that...

Yes, so I recently ported `TestReadOnlyAndAllCommittedMessages` to use a sarama implementation for both producer and consumer — previously it was using a custom .jar to provide the commit+rollback of transactional...

If you're using the consumer group functionality, Kafka will track your committed offset(s) for you. When your consumer group goes down and comes back again, it will start reading from...

@eafzali we are basically ready to cut a release, but we were waiting for more confirmation that github.com/Shopify/Sarama@main fixed the issue for people before cutting the release. Have you managed...

@faec thanks for taking the time to send these fixes over, it's much appreciated! The only one I'm not sure about is the old workaround for Azure's OffsetFetchResponse behaviour, as...

@pkoutsovasilis yes that sounds interesting, please do raise an issue. Hearing from users who are consuming from multiple topics (potentially of differing partition numbers) from the same consumer group is...

@ppatierno this should now be available on main thanks to @k-wall and will be in the next upcoming release version of Sarama