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],
I agree with Heiko on this one - import context.dispatcher is used
everywhere. It is mentioned in the docs not to close over 'context' and
access it outside of message handlers, however I think more education is
needed here.
On Wednesday, March 7, 2018 at 5:35:05 PM UTC-8, Konrad Malawski
Dear hakkers,
we are happy to announce Akka Http 10.1.0, the first release of the 10.1.x
series.
See the announcement
at https://akka.io/blog/news/2018/03/08/akka-http-10.1.0-released.
The most important changes are:
- The new client pool implementation introduced in 10.0.11 is now
It depends on the cluster based tool you are using if it can make use of
weakly up nodes or not. For example routers and distributed data can use
weakly up, while singleton and sharding requires fully up.
The advantage is that you can start using the weakly up nodes for some
tasks without waiting
I think it will be difficult to support the ordinary scheduler in
BehaviorTestKit but perhaps we could use the manual scheduler:
https://doc.akka.io/docs/akka/current/typed/testing.html#controlling-the-scheduler
Please create an issue at https://github.com/akka/akka/issues/new
Thanks,
Patrik
On
