These are chat archives for akkadotnet/akka.net

16th
Feb 2015
Andrew Skotzko
@skotzko
Feb 16 2015 05:23
worth a look
Roger Johansson
@rogeralsing
Feb 16 2015 07:09
@skotzko I'm almost done converting the old generator to use that.. pretty slick... grunt + a couple of NPM modules
Roger Johansson
@rogeralsing
Feb 16 2015 07:23
@skotzko take a look at: https://github.com/rogeralsing/AkkaSiteTake2 you should be able to use that to try local site generation, just run grunt in the repo root
Roger Johansson
@rogeralsing
Feb 16 2015 09:22
atommarkdown.png
@skotzko darn, the markdown support in Atom.io is perfect :)
oh and its live updating also
Natan Vivo
@nvivo
Feb 16 2015 11:26
Amazing!
Andrew Skotzko
@skotzko
Feb 16 2015 16:59
@rogeralsing amazing!
Andrew Skotzko
@skotzko
Feb 16 2015 18:36
@all notes from the contributors meeting last week / road to 1.0 >> http://petabridge.com/blog/akkadotnet-road-to-v1/
throw some RT love at it if you would >> https://twitter.com/askotzko/status/567391657192988672
Aaron Stannard
@Aaronontheweb
Feb 16 2015 19:19
@rogeralsing do we have any serialization verification for ActorSelection?
I've been debugging a failing MultiNodeTest in Akka.Cluster and after days of digging through it, looks like the culprit is that actor selection paths get truncated during remote sends sometimes
Roger Johansson
@rogeralsing
Feb 16 2015 19:21
Oh, not sure, Ill have a look
Aaron Stannard
@Aaronontheweb
Feb 16 2015 19:21
I'm checking the remoting system now
to see if it's an issue there
Roger Johansson
@rogeralsing
Feb 16 2015 19:22
Any specific format? Absolute or relative paths?
Aaron Stannard
@Aaronontheweb
Feb 16 2015 19:22
it's an absolute path - here's the offending line from Akka.Cluster (getting the link)
RootActorPath for a /system actor on a remote host
I've verified that the message is received on the remote host's EndpointReader
but the actor path shows up as the root guardian
missing all of the other parts of the selection
so the message is never delivered to the actor expecting it - gets marked as unhandled by the root guardian
Aaron Stannard
@Aaronontheweb
Feb 16 2015 19:28
going to dig a little deeper on the remoting end RQ
looks like the selection is getting preserved over the wire, but it's still not getting delivered
hopefully it's something stupid
I've been trying to fix this failing test since Friday :facepunch:
Roger Johansson
@rogeralsing
Feb 16 2015 19:39
You are right, actor selection seems to break when deserializing it, I get deadletters as anchor for the selection..
nvm, im stupid
Aaron Stannard
@Aaronontheweb
Feb 16 2015 19:43
nvm, so am I
the actor selection is getting resolved correctly
looks like it's a problem with the Cluster Daemon
Roger Johansson
@rogeralsing
Feb 16 2015 19:46
it was however not possible to create an actor selection to a made up address when running a local system since the actorselection tries to resolve the root guardian of the remote system, and with local provider, it cant, so it gives deadletters
Andrew Skotzko
@skotzko
Feb 16 2015 19:50
@Aaronontheweb @rogeralsing threw the road to 1.0 post on r/dotnet also
Roger Johansson
@rogeralsing
Feb 16 2015 20:05
:+1:
@skotzko the site builder should now start server and open webpage
Aaron Stannard
@Aaronontheweb
Feb 16 2015 20:54
@smalldave realized with the InitialHeartbeatSpec that the issue is that the barrier coordinator bails out early for some reason
the test is a bit weird - allocates a special node just for the controller which doesn't join the cluster itself
rewrote a massive chunk of remoting while trying to debug that test. Brought everything up to code with canonical Akka
IPriorityMessage and adaptive backoff
as well as the throttler / failure injector
Aaron Stannard
@Aaronontheweb
Feb 16 2015 23:52
that'd make for a good blog post
turning TPL errors into messages
avoiding the pain and agony of AggregateException