Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Activity
  • 14:40
    cptjazz synchronize #3974
  • 14:07
    cptjazz opened #3974
  • 08:30
    ismaelhamed commented #3937
  • Oct 12 15:50
    IrvinDominin opened #127
  • Oct 11 18:21
    Aaronontheweb commented #3973
  • Oct 11 18:20
    Aaronontheweb commented #3937
  • Oct 11 18:16
    Zetanova commented #3937
  • Oct 11 18:11
    Zetanova commented #3937
  • Oct 11 15:09
    Aaronontheweb commented #3937
  • Oct 11 15:08
    Aaronontheweb commented #3937
  • Oct 11 14:36
    Aaronontheweb commented #3973
  • Oct 11 01:00
    Horusiath commented #3057
  • Oct 10 20:02
    IgorFedchenko synchronize #3973
  • Oct 10 19:59
    IgorFedchenko synchronize #3973
  • Oct 10 19:58
    IgorFedchenko commented #3973
  • Oct 10 19:53
    IgorFedchenko opened #3973
  • Oct 10 14:04
    stijnherreman commented #3057
  • Oct 10 13:54
    Aaronontheweb commented #3970
  • Oct 10 13:54
    Aaronontheweb synchronize #3970
  • Oct 10 10:10
    Zetanova commented #3937
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
when you're using 1.1.36
and delete it if it's there
David Rivera
@mithril52
Hmm, ok
Aaron Stannard
@Aaronontheweb
could have been added when you upgraded to 1.2
David Rivera
@mithril52
But I should be using 1.136?
Aaron Stannard
@Aaronontheweb
yep
that's what we support today
David Rivera
@mithril52
Okay
Yup, loosk like thats it. It added rebindings to every project
David Rivera
@mithril52
Thanks Aaron, that fixed it. I hate it when I'm too deep into an issue to see the issue staring me in the face :)
Aaron Stannard
@Aaronontheweb
you're welcome man
some words of advice
it's almost always something stupid
when it comes to mystifying issues like that
David Rivera
@mithril52
Yup, it almost always is :)
Aaron Stannard
@Aaronontheweb
I can't tell you the number of times I've destroyed a build queue because something snuck a dependency into my .CSPROJ that wasn't supported by the build server
personal favorite was causing the server to explode because a user submitted a powershell script that contained some German characters
David Rivera
@mithril52
Heh, ouch
Aaron Stannard
@Aaronontheweb
(on an internal project)
Marc Piechura
@marcpiechura
Ößäü 😜
Aaron Stannard
@Aaronontheweb
:fire: :fire: :fire:
fire burning fire burning on the buiiiiiiiiiiiiiiiild server
saxophone solo
David Rivera
@mithril52
The magic smoke is getting out!
Aaron Stannard
@Aaronontheweb
I told you not to use unicoooooooooooooooooooode
Sergey Prytkov
@Rattenkrieg
@Aaronontheweb it seems I've encountered wrongly constructed spec while being looking for example for docs
If these nodes supposed to gain separate gating duration each like First - 1d; Second - 1s then there should be two distinc NodeConfig calls per each role
Aaron Stannard
@Aaronontheweb
ah
mind submitting a PR to fix that?