Re: [akka-user][deprecated] Akka Streams Resuming Materializer does not log exceptions

Hi Konrad, Thanks for your response. I have started a thread in discuss.lightbend as suggested by you. I've posted a follow-up question on that. Looking forward for your reply. Thanks, Dolly On

[akka-user][deprecated] Akka Streams Resuming Materializer does not log exceptions

Hello all, When I provide a resuming materializer to the stream, the exceptions that occurred in the stream do not get logged. Is there any way to log these exceptions ? import akka.actor.ActorSystem import akka.stream.scaladsl.Source import akka.stream.{ActorMaterializer,

Re: [akka-user] Akka Typed BehaviorTestKit with TimerScheduler

Thanks, Patrick. For now, we have used a workaround by mocking a TimerScheduler instance as below: val timerScheduler = mock[TimerScheduler[MyMessage]] doNothing() .when(timerScheduler) .startSingleTimer( ArgumentMatchers.eq(MyBehavior.TimerKey), ArgumentMatchers.any[MyMessage],

[akka-user] Akka Typed BehaviorTestKit with TimerScheduler

Hi, We are trying to create a BehaviorTestKit using a behavior which spawns a timer within. val behaviorTestKit = BehaviorTestKit(createBehavior) private def createBehavior(): Behavior[MyMessage] = { Behaviors .withTimers[MyMessage]( timerScheduler ⇒ Behaviors

Re: [akka-user] [Akka Streams] Difference between KillSwitch and Materializer.shutdown()

This was helpful. Thank you! On Monday, February 19, 2018 at 6:04:45 PM UTC+5:30, Konrad Malawski wrote: > > First warning sign: Why would you have one stream per materializer? > > shutting down the materializer while things are running is very brutal. > It’s like forcefully pulling the carpet

[akka-user] [Akka Streams] Feedback on custom throttle stage

Hi all, We are trying to create a stage which caters to 2 requirements - 1) If the producer is faster than the consumer, then consumer should get the latest element always (dropping the intermediate elements). Similar to conflate

[akka-user] [Akka Streams] Difference between KillSwitch and Materializer.shutdown()

I came across 2 ways to terminate a stream 1. KillSwitch 2. Materializer.shutdown() I see one difference which is - Materializer.shutdown() is used to kill all streams materialized by that materializer whereas KillSwitch can be used to terminate one particular stream. In