Tommy Brunn

The second error you mentioned is interesting. Could you [set up a listener for the `CRASH` event](https://kafka.js.org/docs/instrumentation-events#a-name-consumer-a-consumer) and log out not just the error message, but also `error.stack`? The error...

@Kannndev: I don't think your issue is the same. Since you're using a custom partition assigner, my bet would be that it's returning something that's not a valid assignment, and...

There's no need to call `consumer.commitOffsets` from within `eachMessage`. A soon as `eachMessage` resolves the offset will be committed automatically: ```ts await consumer.run({ eachMessage: async ({topic,partition,message}) => { await insert(JSON.parse(message.value.toString("utf-8")));...

I have a hypothesis, but without more information, it's very difficult to know if this is indeed the issue. At least it could be some place to start. Offset out...

The `sendOffsets` method is there to be able to commit offsets only if the transaction is successful. To use this, you have to turn off automatic committing and manually commit...

This feels incredibly familiar, like we worked on this bug before, but maybe I'm just having dejavu. Related issues from other clients: * https://github.com/zendesk/ruby-kafka/issues/555 * https://github.com/dpkp/kafka-python/issues/1701 EDIT: I knew I...

I'm not sure I will have the time to look into this myself, but a way to reproduce the issue would be great. The relevant topic configuration would be a...

> Is there a way we can help solve it? Like I mentioned a year ago, a way to consistently reproduce the issue is the best way to resolve it....

> It seems like there was an unannounced breaking change that requires producer.connect to be called before sending? This has always been the case. We have never supported sending messages...

You should just connect at startup and disconnect at shutdown. There seems to be a bug introduced with the latest version related to reconnects, but regardless, nothing is changing about...