Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Activity
  • 06:35
    dependabot-preview[bot] labeled #128
  • 06:35
    dependabot-preview[bot] opened #128
  • 06:35

    dependabot-preview[bot] on nuget

    Bump MongoDB.Driver from 2.10.2… (compare)

  • Apr 07 22:47
    PiotrJustyna commented #4368
  • Apr 07 22:13
    PiotrJustyna opened #4371
  • Apr 07 19:14
    PiotrJustyna commented #4368
  • Apr 07 17:03
    Arkatufus closed #4368
  • Apr 07 15:55
    dependabot-preview[bot] synchronize #3986
  • Apr 07 15:55

    dependabot-preview[bot] on nuget

    Bump NUnit from 3.6.1 to 3.12.0… (compare)

  • Apr 07 15:55
    dependabot-preview[bot] synchronize #4337
  • Apr 07 15:55

    dependabot-preview[bot] on nuget

    Bump FSharp.Quotations.Evaluato… (compare)

  • Apr 07 15:55
    dependabot-preview[bot] edited #4337
  • Apr 07 15:55
    dependabot-preview[bot] edited #3986
  • Apr 07 15:54
    dependabot-preview[bot] edited #4337
  • Apr 07 15:54
    dependabot-preview[bot] edited #3986
  • Apr 07 15:53

    dependabot-preview[bot] on dev

    Bump BenchmarkDotNet from 0.12.… (compare)

  • Apr 07 15:53

    dependabot-preview[bot] on nuget

    (compare)

  • Apr 07 15:53
    dependabot-preview[bot] closed #4370
  • Apr 07 15:53
    Aaronontheweb commented #4370
  • Apr 07 14:59
    PiotrJustyna commented #4368
Arjen Smits
@Danthar
and send any responses from that, back to the website
Thats what i meant with that your proxy would have to be specifically engineered to suit its role as a proxy for your website.
And thats why there is no generic cluster proxy thingy
Vlad Kosarev
@vladkosarev
Remoting doesn't work for azure websites right now anyway so you can't even do that
Arjen Smits
@Danthar
If remoting does not work, then clustering would not work either, since it uses the same infrastructure underneath
Vlad Kosarev
@vladkosarev
yes, clustering never worked, remoting broke in 1.1
remoting has been fixed in dev branch but hasn't been released yet
Arjen Smits
@Danthar
ah, yep
Mike Johnson
@softwaremike
Are you saying remoting doesn't work at all in 1.1 or just for azure websites? I just updated my 1.0 project to 1.1.1 a few minutes ago and we use remoting between several processes..
Bartosz Sypytkowski
@Horusiath
@softwaremike v1.1.1 works normally. @Danthar meant azure websites. Do we have ticket for that?
Arjen Smits
@Danthar
@Horusiath I am not sure. It has come up several times. But i think it was related to a bug in how we resolved hostname's at first, and later on ipv6 issues. Which afaik both have been resolved
I think this played largely during your vacation ;)
Mike Johnson
@softwaremike
@Horusiath OK thanks!
Next problem - I upgraded all my projects across the board to 1.1.1. When the actor system starts up, I now get this exception:
Logger [Akka.Event.DefaultLogger] specified in config cannot be loaded:
System.MissingMethodException: Method not found: 'System.Type Akka.Dispatch.Mailboxes.GetMailboxType(Akka.Actor.Props, Akka.Configuration.Config)'.
at Akka.Remote.RemoteActorRefProvider.ActorOf(ActorSystemImpl system, Props props, IInternalActorRef supervisor, ActorPath path, Boolean systemService, Deploy deploy, Boolean lookupDeploy, Boolean async)
at Akka.Actor.ActorCell.MakeChild(Props props, String name, Boolean async, Boolean systemService)
at Akka.Actor.ActorCell.AttachChild(Props props, Boolean isSystemService, String name)
at Akka.Actor.Internal.ActorSystemImpl.SystemActorOf(Props props, String name)
at Akka.Event.LoggingBus.AddLogger(ActorSystemImpl system, Type loggerType, LogLevel logLevel, String loggingBusName, TimeSpan timeout)
at Akka.Event.LoggingBus.StartDefaultLoggers(ActorSystemImpl system)
My HOCON config is very simple:

akka {
actor {
provider = "Akka.Remote.RemoteActorRefProvider, Akka.Remote"
}

remote {
    helios.tcp {
        port = 8092
        hostname = localhost
    }
}

}

Mike Johnson
@softwaremike
Anyone seen this exception before?
Mike Johnson
@softwaremike
Never mind, ignore that... one of my projects still had Akka.Remote 1.0.8 it its references :) oops!
riawz
@riawz

I have an actor which itself loops, like GetMsg, ProcessMsg, if GetMsg is not null, then pass to ProcessMsg, otherwise, wait for a few seconds then tell itself to GetMsg again

what's the best way to test this kind of workflow?

GetMsg and ProcessMsg are two separate actors, which ProcessMsg is created by GetMsg
Peter Hvidgaard
@hvidgaard
Anyone have experience with SimpleInjector and Akka.net together? I'm getting "Do not create actors using 'new', always create them using an ActorContext/System" when the container is verified.
I initialize like this
container.Register<QueryDataStoreActorBase, QuerySqlDataStore>();
var system = ActorSystem.Create("ActorSystem");
system.AddDependencyResolver(new SimpleInjectorDependencyResolver(container, system));
container.RegisterSingleton(system);
riawz
@riawz
is there a way to ExpectMsg<MsgType>() multiple times?
Arjen Smits
@Danthar
@hvidgaard system.AddDependencyResolver(new SimpleInjectorDependencyResolver(container, system)); is wrong
Just calling var resolver = new SimpleInjectorDependencyResolver(container, system); is enough
it registers itself with the system
the system.AddDepedencyResolver is a public api exposed for the DI plugins to use. It should not be used directly. Although it is possible, if you know what you are doing.
Peter Hvidgaard
@hvidgaard
@Danthar Alright, removed that line, but the example still fails because SI creates all registered dependencies during verification.
Arjen Smits
@Danthar
@riawz ExpectMsgAllOf ??
Oh? thats odd.
riawz
@riawz
actually, I don't need it, I have actor A which creates actor B, B is roundrobin, but when I'm testing, I can only test against a single instance of actor B, so I don't need it, thanks
A will receive 2 response from 2 B instances, that's what I was thinking of testing but I can't find a way to "mock" router using testkit
Arjen Smits
@Danthar
@hvidgaard it looks like the SimpleInjector plugin is still on 1.0.8 ?
The tests work. So plugin integration for 1.0.8 looks good
Peter Hvidgaard
@hvidgaard
I've updated to the latest akka.net packages, I assumed that a minor version increase wasn't a problem.
Arjen Smits
@Danthar
Have you ran the tests ?
Peter Hvidgaard
@hvidgaard
no, I've used the NuGet packages.
Arjen Smits
@Danthar
That would be a problem :P
If you upgrade, you should rebuild the plugin against the latest akka.net packages
Peter Hvidgaard
@hvidgaard
okay, good to know...
Arjen Smits
@Danthar
I just forked the repo and got the env open just now. ill check for you
It looks ok.
I gtg, got a meeting
Peter Hvidgaard
@hvidgaard
alright, playing with it myself. Thanks so far
Arjen Smits
@Danthar
but if you update the repo to have the plugin use the latest akka.net. And build a version explicitly targetting it, that should work
also check the tests project of the plugin, for details on how to register dependencies
could be the readme is wrong