[akka-user] streams: why pulls the concat combinator both sides eagerly and the merge combinator not

Hi, I stumbled accross the surprising behaviour that the concat combinator uses so called "detached" inputs that pull eagerly (without signalled demand; effectively being a buffer of size 1). The comment indicates that this is a means to avoid deadlocks in graphs with cycles. Yet, when

[akka-user] invalid materialized value

Hi all, the following line of code val ((pub, mat), sub) = TestSource.probe[Int].viaMat(Flow[Int])(Keep.both).toMat(TestSink.probe)(Keep.both).run() throws a ClassCastException: java.lang.ClassCastException: akka.stream.testkit.TestPublisher$Probe cannot be cast to scala.Tuple2 it seems

[akka-user] Akka Http ResponseTimeout

Hi all, what is the recommended (correct?) way to ensure a certain response timeout when using superPool flow? I think flow.completionTimeout (and friends) are not apropriate because they affect the whole flow of requests to responses whereas only a single request-response pair might have been

[akka-user] Completion of a Graph with a Cycle

Hi all, is there a principled way to complete a graph that contains a cycle? The basic problem is that the initial Merge component can either complete eagerly or not. Both settings are suboptimal (if it completes not eager it will complete never, if it completes eager elements in the feedback