These are chat archives for akkadotnet/akka.net

18th
Apr 2017
Michael Chandler
@optiks
Apr 18 2017 01:30
@Aaronontheweb, commit 69709352
....changes the CreateTestProbe() behaviour to create the test actor under system, instead of user. Is this a deliberate change?
This breaks some of tests which rely on ActorSelection.
TestKitBase.cs:449 FYI
Daniel Söderberg
@raskolnikoov
Apr 18 2017 06:41
@Danthar @Horusiath @Aaronontheweb what's the difference between Akka.Testkit.Xunit/Xunit2 ?
Marc Piechura
@marcpiechura
Apr 18 2017 06:54
@raskolnikoov the Xunit version it targets ;-)
Lev Lehn
@llehn
Apr 18 2017 07:09
@Cawifre thx
Daniel Söderberg
@raskolnikoov
Apr 18 2017 08:01
can somebody who knows provide an example with Akka.Testkit where the childactors uses Context.DI.Props<T>() ? I get errors on this and dont know how to test my actors where it uses DI
System.NullReferenceException
Alex Valuyskiy
@alexvaluyskiy
Apr 18 2017 08:45
@raskolnikoov there is no difference anymore. Both depend on Xunit2
Aaron Stannard
@Aaronontheweb
Apr 18 2017 14:55
@raskolnikoov although not anymore - as of 1.2 both of them are the same essentially
we dropped support for XUnit1
Arsene Tochemey GANDOTE
@Tochemey
Apr 18 2017 21:04
Hello. I can see the akka stream is now stable. However there is no great documentation or tutorial around. Every time I have to go and read the JVM version and Tuto the JVM guys have put online. Please can you guys who has used well share some real world scenario tutorial that can help we novice in it.
Michael Chandler
@optiks
Apr 18 2017 21:34
@Aaronontheweb any idea if the CreateTestProbe() behaviour change was deliberate? (see more detail above)
fanoI
@fanoI
Apr 18 2017 21:49

Is it possible to launch the UI Event Loop from an Actor? Only if that Actor will exist the GUI should run this works with a Command Line application but not in Akka.Net Actor:

       [STAThread] //optional
        protected static bool StartUILoop()
        {
            Application.Run();
            return true;
        }

        protected override void PreStart()
        {
            /* Let's start an Empty UI Application, the true Application will load the page with "Loading..." */
            //Task mytask = Task.Run(() => Application.Run());

            Task mytask = Task.Run(() =>
                StartUILoop()
            );
        }

then when I receive the load command I simply do:

                    var form = new LoginForm();
                    form.Show();

the form is effectively shown but is not working is not active, label text is not drawn and if I move the mouse in it I get the spin wheel!

Thank you for your help...

I've tried to create the Actor in the UI thread using dispatcher = akka.actor.synchronized-dispatcher but nothing changes I suspect it is because I've created a Task not the normal UI thread
Marc Piechura
@marcpiechura
Apr 18 2017 22:06
@Tochemey we have ported the complete documentation from the jvm too. Can you give me a link with the tutorials your referring to?
Arsene Tochemey GANDOTE
@Tochemey
Apr 18 2017 22:18

@Silv3rcircl3 I have gone through few of them.
https://www.slideshare.net/Lightbend/understanding-akka-streams-back-pressure-and-asynchronous-architectures?next_slideshow=1

https://www.slideshare.net/rolandkuhn/akka-streams-and-http

https://github.com/pkinsky/akka-streams-example

https://www.slideshare.net/joy87/a-dive-into-akka-streams-from-the-basics-to-a-realworld-scenario

The documentation is great. I am disputing that. However you gusy have used in production if you guys can write some tutos like the one Bartosz wrote on Akka.IO it will help us as starting point.

Marc Piechura
@marcpiechura
Apr 18 2017 22:32
The example from pkinsky is probably worth porting it. I think the only one that is using Akka.Streams in production is @Aaronontheweb ;-) And we have the webcrawler example that is now using Akka.Streams, see petabridge/akkadotnet-code-samples@fcc6025
Aaron Stannard
@Aaronontheweb
Apr 18 2017 22:33
@optiks the change was deliberate
ensures that the test probes and test actors only get shut down after the user-defined actors
did that end up breaking some of your specs?
(it also was meant to bring us in line with the JVM)
Michael Chandler
@optiks
Apr 18 2017 23:15
@Aaronontheweb Okie, thanks. Yep, it broke some of tests which were testing code which was using ActorSelection