Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Activity
  • 03:08
    hhko commented #4094
  • Dec 13 21:37
    Aaronontheweb commented #4085
  • Dec 13 20:28
    IgorFedchenko commented #4085
  • Dec 13 20:27
    IgorFedchenko commented #4085
  • Dec 13 15:38
    Aaronontheweb labeled #4096
  • Dec 13 15:38
    Aaronontheweb milestoned #4096
  • Dec 13 15:38
    Aaronontheweb labeled #4096
  • Dec 13 15:38
    Aaronontheweb opened #4096
  • Dec 13 10:41
    peirens-bart opened #4095
  • Dec 13 08:37
    Aaronontheweb synchronize #4071
  • Dec 13 08:13
    jiyeongj opened #4094
  • Dec 12 15:42
    Aaronontheweb synchronize #4086
  • Dec 12 15:42
    Aaronontheweb closed #4083
  • Dec 12 15:42

    Aaronontheweb on dev

    Fix #4083 - Endpoint receive bu… (compare)

  • Dec 12 15:42
    Aaronontheweb closed #4089
  • Dec 12 15:42
    Aaronontheweb labeled #4093
  • Dec 12 15:42
    Aaronontheweb labeled #4093
  • Dec 12 15:42
    Aaronontheweb labeled #4093
  • Dec 12 15:42
    Aaronontheweb opened #4093
  • Dec 12 14:20
    Aaronontheweb commented #4092
Maxim Cherednik
@maxcherednik
in there I have a similar situation
I've got this main actor: WidgetManagerActor
and when it starts it sends a message to itself, which does some complicated logic of sending messages to someone else and having responses back
I am not sure if it's easy to comprehend
check this one for instance: WhenWidgetConfigurationProviderFailsShouldRetry
or this one: InitWidgetManagerActorWithSeveralWidgets
so the idea is that you send a message to the child actor and you should be prepared that it will never reply....
Maxim Cherednik
@maxcherednik
in this case you need to have backup logic of retry...
do you follow? :)
Daniel Söderberg
@raskolnikoov
yes I follow
Maxim Cherednik
@maxcherednik
for instance in my WidgetManagerActor I am injecting the actor, so it's not exactly a child.... but I need it this way.... in you case you can have a Props param from the constructor....
in the prod code - you set the real child actor's props, in the test code you have a props of the TestProbe
Daniel Söderberg
@raskolnikoov
yes.. but I will have to rewrite my test case for this. Thanks for the help! :)
Maxim Cherednik
@maxcherednik
you will probably need to rewrite lots of things :)
but anyhow... try it... other than this, I don't know how to handle this
Daniel Söderberg
@raskolnikoov
I talked to Roger Johansson about this now and he answered that it's not possible to do my test case.
Maxim Cherednik
@maxcherednik
yeah - like you described - not possible...
Aaron Stannard
@Aaronontheweb
@Rattenkrieg I haven't seen any examples of this being needed in practice
but with your changes to the MNTR in #2502
is it still possible to give one node amongst the others in the spec its own configuration?
I.E. if I wanted to run a test that gave one node a different configuration from the others?
I kind of think this is YAGNI to some extent, but still - that's a capability we had before that I would like to preserve in some capacity
in case you missed it, YAGNI
Aaron Stannard
@Aaronontheweb
ah nice
do you mention how to do that on the documentation PR you sent in|?
(haven't looked at it yet)
Sergey Prytkov
@Rattenkrieg
Nope, but this part isn't one that was affected by my changes
Aaron Stannard
@Aaronontheweb
cool, good to know
Sergey Prytkov
@Rattenkrieg
Feel free to ask to add any part to docs
Aaron Stannard
@Aaronontheweb
could you add a section on configuring individual nodes?
as part of the section where you define a MultiNodeConfig?
doesn't need to be much, just a small example would be great
the PR was great btw, definitely like the look of the logs much more now
Sergey Prytkov
@Rattenkrieg
Thanks!
NodeConfig(new List<RoleName> { First }, new List<Config> { ConfigurationFactory.ParseString("akka.cluster.roles =[frontend]") });
could you add a section on configuring individual nodes?
Aaron Stannard
@Aaronontheweb
yep, that would be great
something like that
Sergey Prytkov
@Rattenkrieg
Ok got it
Will do after lunch ;)
David Rivera
@mithril52
I seem to be having some issues with Akka and its use of System.Collections.Immutable. If I use 1.2.0 version of Immutable, when I go to create my actor system with a provided config object, it throws an exception saying it cannot find Immutable 1.1.36. Then if I change the Immutable version to 1.1.36, it says it can't find version 1.2.0 of Immutable. Has anyone else come across an issue like this?
Aaron Stannard
@Aaronontheweb
@mithril52 which modules are you using?
all of the shipped Akka.NET modules depend on 1.1.36
David Rivera
@mithril52
Cluster, DI.Core, DI.Ninject, Logger.Serilog, Remote, Testkit, TestKit.XUnit
All 1.1.3
Well, exc ept Serilog. Its at 1.12
1.1.2
Aaron Stannard
@Aaronontheweb
although we're looking at upgrading to the latest here: akkadotnet/akka.net#2509
IMHO, check to see if you have a binding redirect defined in App.config