{"push_id":1459074978,"size":1,"distinct_size":1,"ref":"refs/heads/multiple_consumption_bugfix","head":"96251d71a0e38de9ca6b187ea4649a5e8489a687","before":"0cd295559f0bc387ccfcfe1aac28ae610f089e60","commits":[{"sha":"96251d71a0e38de9ca6b187ea4649a5e8489a687","author":{"name":"Alex Adriaanse","email":"af52d3065b8b78750f844012b8e34dbc454a5a0a@oseberg.io"},"message":"Allow consumeFirstStringMessageFrom to be called multiple times\n\nIn v0.5.0 you were able to call consumeFirstStringMessageFrom multiple\ntimes, with each invocation causing the next message in a topic to be\nconsumed. In v0.10.0 this was no longer the case: the first invocation\nworks fine, but subsequent invocations would result in exceptions as the\nfirst invocation would cause *all* messages to be committed even though\nonly the first one is returned, leaving no messages remaining to be\nconsumed by subsequent calls. This regression was likely introduced by\ncommit a90674307eb15206e4f75619beae067124d989d6.\n\nThis commit fixes this by disabling auto-commit by default and simply\ncommitting only the message that consumeFirstStringMessageFrom returns.","distinct":true,"url":"https://api.github.com/repos/alexadriaanse/scalatest-embedded-kafka/commits/96251d71a0e38de9ca6b187ea4649a5e8489a687"}]}
{"actor":{"display_login":"alexadriaanse"}}