Sean Glover

Caused by a race condition accessing "metrics" from the `MetricsControl` in the `"access metrics"` test of `IntegrationSpec`. The test calls into a mixed in method (`MetricsControl.metrics`) before the `GraphStageLogic` has...

``` [info] - must access metrics *** FAILED *** (80 milliseconds) [info] java.lang.IllegalStateException: not yet initialized: only setHandler is allowed in GraphStageLogic constructor. To access materializer use Source/Flow/Sink.setup factory [info]...

Apologies for the late reply. This could be related to https://github.com/akka/alpakka-kafka/pull/742 . @mehdimas could you please test against master?

> does this mean as of Alpakka Kafka Version 2.0.2, `ProducerMessage.multi(...)` would produce duplicates in the destination topics when used with a `Transactional.source` connected to a `Transactional.flow`? This should not...

@kolapkardhaval All messages produced to Kafka within a transaction will be committed as part of the same transaction. If a message is produced, but not acknowledged the transaction won't be...

@szymonm Thanks for raising this issue. > `SingleSourceLogic` clears the buffer of accumulated records of revoked partitions only after new partitions are assigned. I think that this causes blocking `onRevoke`...

@szymonm This sounds reasonable to me. To rephrase for my own understanding: You would like to filter buffered messages that have not been emitted from the Transactional Source, but keep...

> We also have a bunch of tests on our side that discovered issues with transactions before. It would be great to get an idea of the issues you've experienced,...

Hi @gabrielreid. Yes, this is a recurring issue for users that often comes up. As you mentioned, users can introduce an arbitrary number of asynchronous boundaries in their graph, which...

Ok, I'm looking forward to seeing an implementation.