ghilainm

For me it doesn't guarantee anything. Reading the code just shows that indeed it is in the unit of work, but they are corner cases where you will be able...

I am totally fine with what you said. I am referring to consistency guarantees between the two stores (Kafka and PostgreSQL). So now consider the case where you can commit...

> That's why we are executing Kafka work only after the current unit of work is committed, i.e. uow.afterCommit. @nklmish But then you may end up with events not committed...

@nklmish I was wondering if implementing the KafkaPublisher as a TrackingEventProcessor would not be a better solution. It would allow to have at least one guarantee of delivery if the...

@abuijze No problem. But I think that in this case the documentation must be improved in order to explain such 'limitation' in the guarantees offered by the Kafka publisher that...

Thanks for your answer. In the mean time I figure out the issue on my side. The problem was when integrating it in gitlab ci. I had to change the...

Seems good to me!

I have the same issue as you. The problem seems to be linked to the :asciidoctorGemsPrepare tasks. When I do: `./gradlew clean asciidoctorRevealJs --no-build-cache` It always works fine. So it...

Same issue with asciidoctorRevealjs

This is the answer I found somewhere else: ``` val repositoriesInternal = repositories as ExtensionAware repositoriesInternal.extensions.configure(com.github.jrubygradle.api.core.RepositoryHandlerExtension::class) { gems() } ``` However this should be documented imo.