Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Activity
  • Jan 15 20:23
    object commented #190
  • Jan 15 14:22
    Aaronontheweb milestoned #4720
  • Jan 15 14:22
    Aaronontheweb labeled #4720
  • Jan 15 14:22
    Aaronontheweb labeled #4720
  • Jan 15 14:22
    Aaronontheweb opened #4720
  • Jan 14 15:53
    object opened #190
  • Jan 14 08:10
    object commented #4265
  • Jan 14 08:04
    object commented #4265
  • Jan 13 16:35

    Aaronontheweb on 1.4.14

    (compare)

  • Jan 13 16:31

    Aaronontheweb on master

    Bump Mongo2Go from 2.2.14 to 2.… Bump MongoDB.Driver from 2.11.4… Bump Microsoft.NET.Test.Sdk fro… and 4 more (compare)

  • Jan 13 16:31
    Aaronontheweb closed #176
  • Jan 13 16:30
    Aaronontheweb opened #176
  • Jan 13 16:30

    Aaronontheweb on 1.4.14

    (compare)

  • Jan 13 16:30

    Aaronontheweb on dev

    Added v1.4.14 release notes (#1… (compare)

  • Jan 13 16:30
    Aaronontheweb closed #175
  • Jan 13 16:16

    Aaronontheweb on dev

    ensure that all recovered Times… (compare)

  • Jan 13 16:16
    Aaronontheweb closed #174
  • Jan 13 16:06
    Aaronontheweb synchronize #174
  • Jan 13 15:52
    Aaronontheweb opened #175
  • Jan 13 15:52

    Aaronontheweb on 1.4.14

    Added v1.4.14 release notes (compare)

Aaron Stannard
@Aaronontheweb
needed it to inject actor references into controllers
Scott Martin
@Scott__Martin_twitter
ah, good point
Is there a common pattern for injection messages from outside the ActorSystem?
Aaron Stannard
@Aaronontheweb
you can always pass a message to any IActorRef from anywhere
Scott Martin
@Scott__Martin_twitter
For now the static ref isn't so bad as it is to only maintain backwards compatibility for the time being.
Aaron Stannard
@Aaronontheweb
and any top-level actors declared via ActorSystem.ActorOf are easily passable to external contexts
Scott Martin
@Scott__Martin_twitter
@Aaronontheweb Thank you for the information!
Aaron Stannard
@Aaronontheweb
@alexvaluyskiy figured out that consistent hash router race condition
it's a side-effect of having that actor start as a RepointableActorRef
if the actor cell doesn't start right away (talking like nanoseconds here)
the call to check to see how many children the router has, the first call, will fail
because the actor startup is asynchronous now
I think I can fix that
Aaron Stannard
@Aaronontheweb
(TL;DR; it's an issue with how the test is designed)
Aaron Stannard
@Aaronontheweb
added a fix just now akkadotnet/akka.net#2112
qwoz
@qwoz
what's the best way to visualize the actor hierarchy when debugging? Something akin to Visual Studio's Locals tab where you can drill down a tree structure to find something like:
MyActorSystem > user > MyActor > ChildActor > OtherActor [terminated]
Aaron Stannard
@Aaronontheweb
nothing built into Akka.NET for that
but what you can do inside the VS debugger
is grab ahold of the Context
inside a watch
and then expand the Children collection, whatever it is called
and from there you should be able to do that recursively for local actors at least
qwoz
@qwoz
yeah, I can do this crudely when debugging a test using this > base > base > base > Sys > base > Guardian > base > Children ... was hoping there was something a tad nicer. :smile:
to11mtm
@to11mtm
@qwoz, not sure if it would help for your use case but have you seen the visualizer? https://www.nuget.org/packages/Akka.Visualizer/
fouimette
@fouimette
Hello!
I am running through a tutorial on PluralSight (that is a little outdated) and am using the Terminate() method followed by the WhenTerminated task. What I get is a "DeathWatchNofitification message was not delivered" error. Any thoughts?
fouimette
@fouimette
blob
Bartosz Sypytkowski
@Horusiath
@fouimette usually it's nothing to worry about. When actor system terminates, it kills all actors in async fashion. Actors build in hierarchies parent-child often send messages to each other when terminating. In case of system termination that means that one terminating actor could send a message to another, which is being terminated too.
Corneliu
@corneliutusnea
Hi guys, what's the status of the Akka Cluster?
Bartosz Sypytkowski
@Horusiath
@corneliutusnea pretty solid already, I think @Aaronontheweb is going to move it out of beta in a week.
Corneliu
@corneliutusnea
Should I wait for final integration / testing with my product ?
Bartosz Sypytkowski
@Horusiath
if it's only a week, I would wait anyway
qwoz
@qwoz
Thanks @to11mtm ... is there a site for Akka.Visualizer with a bit more info?
Corneliu
@corneliutusnea
@qwoz I think you are talking about my visualizer. I really had no time to publish it :/ my fault
Corneliu
@corneliutusnea
fouimette
@fouimette
@Horusiath Thanks for the response. I would expect that a simple demo to create an actor in an actor system and then terminating the system would not produce such an unexpected result.
qwoz
@qwoz
thanks @corneliutusnea
hidavidpeng
@hidavidpeng
hi How can I get recover the message in supervisor?
Bart de Boer
@boekabart
@hidavidpeng either in the 'character' actor you do smth with it in PreRestart (or PostStop), or have the supervisor 'remember' it when sending it to the inner actor, and keep it until 'OK' or 'NOK (deadwatchnotification)'
Ricky Blankenaufulland
@ZoolWay
Can I check if a (cluster) router currently has any routees?
Ricky Blankenaufulland
@ZoolWay
In more words: I would like to know if there is currently any node connected which has actors capable of the job I want to do.
Alex Valuyskiy
@alexvaluyskiy
await router.Ask<Routees>(new GetRoutees())
to11mtm
@to11mtm
@corneliutusnea THANK YOU for putting it on git finally. =D
Stanley Goldman
@StanleyGoldman
are there any screenshots of the visualizer?
Aaron Stannard
@Aaronontheweb
man, amazing what one small change can do in the right place in terms of performance
removed one allocation inside the dispatcher system and saw a bump immediately
Aaron Stannard
@Aaronontheweb
going to add a unit test that does the equivalent of what our NBench specs do for measuring actor message throughput
to make it easier to hook up a profiler like dotTrace, mostly
since NBench doesn't offer that level of granularity
Aaron Stannard
@Aaronontheweb
actually, hmmm... I'm going to need to rethink that