bug in CommitRecords? about franz-go HOT 6 CLOSED

as you see lag always 1 and after i'm restart test last record always processed.

from franz-go.

i have such issue in other kafka driver (segmentio/kafka-go) when commit current record offset and not next offset.
https://kafka.apache.org/22/javadoc/index.html?org/apache/kafka/clients/consumer/KafkaConsumer.html#:~:text=Note%3A%20The%20committed%20offset%20should,of%20the%20last%20message%20processed

can you check this? or i have may be error in my code (but i dont think so)
https://github.com/unistack-org/micro-broker-kgo/blob/master/kgo.go#L486 (this is my code, i'm simply run CommitRecords)

from franz-go.

@twmb i think you need to https://github.com/twmb/franz-go/blob/v0.10.1/pkg/kgo/consumer_group.go#L1687 add +1 to offset from record. in this case you don't have lag with 1 message and not double process last message each time

from franz-go.

i'm check my proposed solution and after r.Offset + 1 in 1687 lag goes to 0 and messages after restart not double processed

from franz-go.

fix #65

from franz-go.

Thank you, very obvious bug, great catch!

from franz-go.