Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Activity
  • Apr 03 22:24
    huzaifak opened #4367
  • Apr 03 21:45
    Aaronontheweb commented #4344
  • Apr 03 05:55
    Lutando commented #4344
  • Apr 02 17:23
    huzaifak commented #4303
  • Apr 02 17:23
    huzaifak closed #4303
  • Apr 02 02:13
    ShawnYun commented #4366
  • Apr 01 17:18
    huzaifak commented #4303
  • Apr 01 14:30
    Aaronontheweb commented #4366
  • Apr 01 14:29
    Aaronontheweb closed #4360
  • Apr 01 14:29
    Aaronontheweb commented #4360
  • Apr 01 06:43

    dependabot-preview[bot] on nuget

    (compare)

  • Apr 01 06:43
    dependabot-preview[bot] closed #151
  • Apr 01 06:43
    dependabot-preview[bot] commented #151
  • Apr 01 06:43
    dependabot-preview[bot] labeled #152
  • Apr 01 06:43
    dependabot-preview[bot] opened #152
  • Apr 01 06:43

    dependabot-preview[bot] on nuget

    Bump AkkaVersion from 1.4.1 to … (compare)

  • Apr 01 06:43

    dependabot-preview[bot] on nuget

    (compare)

  • Apr 01 06:43
    dependabot-preview[bot] closed #125
  • Apr 01 06:43
    dependabot-preview[bot] commented #125
  • Apr 01 06:43
    dependabot-preview[bot] labeled #127
Aaron Stannard
@Aaronontheweb
the seed nodes are there to help automate the formation / join process
Suhas Chatekar
@schatekar
@Horusiath Is replyMap in the lambda of foldLeft is the map returned by the first lambda on which foldLeft is called)?
Aaron Stannard
@Aaronontheweb
@joecojabba we cover this in detail in Petabridge's design patterns training, but the correct answer is that if your actor has a longer lifespan than the dependency it takes (like a database connection) then the actor has to be responsible for fetching / replacing that dependency
so the actor can take a factory method (Func<Neo4JClient> generator) in its constructor or call a static factory somewhere if necessary
the other option is to make it so the actor's lifespan matches the lifespan of the dependency
but you can pay a hefty price when it comes to performance and consistency if you do that - much better to have a long-lived actor that can refresh its db connection
Bartosz Sypytkowski
@Horusiath
@schatekar it this case replyMap is accumulated value. Since in your example immutable map is used, when your calling replyMap + (address -> (replyMap(address) + 1)) you're actually returning new map instance with updated key-value pair. This map is then moved as replyMap to the next iteration of foldLeft
(address -> (replyMap(address) + 1)) is Scala equivalent of C# new KeyValuePair<Address, int>(address, replyMap[address] + 1)
Ivan R. Perez
@irperez
@Aaronontheweb Just a simple reminder to release the nuget package with my bug fix for the Akka.Monitor.PerformanceCounters. Thanks again!
Aaron Stannard
@Aaronontheweb
@irperez petabridge/akka-monitoring#19
waiting on TC to give me a nice green checkmark
then I'll release it
Bartosz Sypytkowski
@Horusiath
did you know that Polish violinist made a song with familiar title :) https://www.youtube.com/watch?v=6Udold4Pj6s
Aaron Stannard
@Aaronontheweb
hehe
Suhas Chatekar
@schatekar
it is nice though
Bartosz Sypytkowski
@Horusiath
yes, nice indeed
Aaron Stannard
@Aaronontheweb
@rogeralsing I had an idea I wanted to run by you
what if instead of having Sender, Self, and Parent always dynamically resolve their state using the current IActorContext
what if we just made them auto-properties and assigned those values each time they were updated?
wouldn't that eliminate the need to have to have a closure when using TPL and PipeTo?
or would we still have that issue? I was wondering if the fact that we're actually invoking a function to return the latest Sender / Self / Parent each time is part of the issue
Scala Akka is able to avoid having to do closures for a lot of this stuff because they just use fields
Aaron Stannard
@Aaronontheweb
@GraemeBradbury I'm still working on debugging #1261 - good news is that you helped me find a bunch of bugs inside our MultiNodeTestKit
might have even fixed the deadlock issue on #1134
Roger Johansson
@rogeralsing
@Aaronontheweb no, 1) they would mutate during the time the tpl task runs, and sender would not be available as an implicit value for Tell. you would have to manually supply it
that last art was 2) :D
part
Aaron Stannard
@Aaronontheweb
hmm... yeah, that'd be true even if Sender was just a dumb field, wouldn't it?
Roger Johansson
@rogeralsing
yepp
Aaron Stannard
@Aaronontheweb
ah... ok
I think that's a JVM / CLR difference then
looks to me like the JVM uses the address of the object being referenced
whereas the CLR looks for the address of a pointer to an object
i.e. the field's pointer
Roger Johansson
@rogeralsing
I think that might have to do with "val" in scala. not sure
Aaron Stannard
@Aaronontheweb
got it
ok well that's good to know
I found a bug in the TestConductor in the multi-node testkit that your Roslyn analyzer also found
caused tests that use throttling to crash
Roger Johansson
@rogeralsing
oh
tlotter
@tlotter
Hi, what is the best way to communicate with a client application (Unity3D .Net 3.5) via a small protocol (ProtoBuf) with an ActorSystem? I read about Akka I/O and was wondering if this is the right way. If so, is there a client library for .Net 3.5 ?
Aaron Stannard
@Aaronontheweb
related to this
Roger Johansson
@rogeralsing
I should probably extend that to look for class member mutations too
Aaron Stannard
@Aaronontheweb
closure bug
@rogeralsing btw, are we actually using akka.actor.ask-timeoutin the C# code anywhere? I want to use that setting to kill off some potential sources of deadlock in the multi-node testkit
I can't find where we're consuming that value
Bartosz Sypytkowski
@Horusiath
@Aaronontheweb if you use Ask without explicit timeout then you're using this setting
Aaron Stannard
@Aaronontheweb
@Horusiath good, that's what I wanted to know - but where in C# do we actually load this setting? Was trying to find a place where we load the ask-timeout key from a Config object
@tlotter at the moment, no - we do not have a general client for Akka.IO just yet
it's D-I-Y