Testing akka, or better yet debugging akka can be a little painful because of timeouts. Something like this http://haacked.com/archive/2014/03/10/master-time-with-reactive-extensions/ (aka explicit time jumps) could be helpful as it would make tests more deterministic and debug-able. Would something like this be possible with akka?
@lavinski_twitter there is a notion of virtual time used for TestScheduler. However this works only with scheduling events. I'm not sure how this would work with timeouts. Akka.net has more complex, non linear execution model. But if someone would propose a solution for this, I'd love to see it.
@Horusiath sure, thanks
weird, Gitter built the history all out of order.
@Aaronontheweb TY for the feedback! I got another Project team at work to start using Akka.NET, I spent an afternoon talking to their lead dev... next morning he had a whole bunch of whiteboard marked up and asked for my help to start rearch =D. Really can't overstate how the proj has done more to re-invigorate us about developing for .NET than anything Microsoft has attempted to do the last 3 years.
@Horusiath @lavinski_twitter Sorry to jump in, but I wonder if the Single-thread-debugging in visual studio would be useful? May keep the threads running remoting/etc from timing out when debugging, admittedly haven't tried.
@to11mtm AFAIK testkit actor system is using a single thread execution anyway
@to11mtm @Horusiath the real pain point is Ask timout out as soon as you resume
@Horusiath I'm also looking at Akkling and my actor takes obj, however if I send a type that I don't cast to obj first it doesn't get handled
That's with sharding (shard, id, must be obj)