Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Activity
  • 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
  • Dec 12 14:14
    Aaronontheweb labeled #4089
  • Dec 12 14:14
    Aaronontheweb labeled #4089
  • Dec 12 14:11
    Aaronontheweb synchronize #4089
  • Dec 12 14:10
    Aaronontheweb synchronize #4086
  • Dec 12 14:09

    Aaronontheweb on dev

    Convert to ImmutableHashSet for… (compare)

  • Dec 12 14:09
    Aaronontheweb closed #4090
  • Dec 12 12:04
    nagytech synchronize #4092
  • Dec 12 11:53
    nagytech synchronize #4092
  • Dec 12 11:49
    nagytech edited #4092
  • Dec 12 11:40
    nagytech opened #4092
  • Dec 12 11:32
    nagytech edited #4091
Onur Gumus
@OnurGumus
and it requires to access to current actor within the current synch context.
what I do is ``` var self = Self; //now I can use self anywhere ````
Stephen Riley
@stephen-riley
within the current synch context
I think that's what I'm not getting.
Onur Gumus
@OnurGumus
Inside the actor if you run another thread like Task.Run ( you can't access to Self any more.
because Self invokes code and requires you to be on the message queue thread of the actor.
Stephen Riley
@stephen-riley
Yes, @OnurGumus , I have the var self = Self; thing, but I don't get why there's at least some Self defined inside the lambda I'm passing to ContinueWith().
because Self invokes code and requires you to be on the message queue thread of the actor.
OOOOOOOH! :-D
me-slove
@me-slove
It sounds like the issue isn't that. It's a closure problem. Assign a local variable and pass that through. You are running a task which means things can change
Stephen Riley
@stephen-riley
If Self is invoking code, I see the opportunity for what I'm seeing.
Okay.
Onur Gumus
@OnurGumus
yes it is. That's why I said offload it by var self = Self;
then you can use it anywhere.
Stephen Riley
@stephen-riley
I'm still not sure why my mylogger ActorSelection isn't carrying context with it, though.
var mylogger = Context.ActorSelection("/user/ConsoleLogger");
Why must I specify my closed-over self as the explicit sender in my call to mylogger.Tell()?
Onur Gumus
@OnurGumus
you don't need.
I thought you were trying to access self.
Stephen Riley
@stephen-riley
var mylogger = Context.ActorSelection("/user/ConsoleLogger");

mylogger.Tell("message");            // this does not work (always from deadLetters)

mylogger.Tell("message}", self);    // this works fine
Onur Gumus
@OnurGumus
that's not normal.
Stephen Riley
@stephen-riley
lol
Good, glad it's not just me. :smile:
Onur Gumus
@OnurGumus
No it's just you.
Stephen Riley
@stephen-riley
lol
Onur Gumus
@OnurGumus
You are probably doing some thing wrong.
Stephen Riley
@stephen-riley
Agreed. :wink:
Onur Gumus
@OnurGumus
mylogger.Tell("message"); // this should just work
Stephen Riley
@stephen-riley
Was hoping someone here would say "oh yeah, do x-y-z and you're fine". Guess I'll pull down source and deep-dive.
Onur Gumus
@OnurGumus
instead try to simplify and isolate the case.
I am sure you will find.
Stephen Riley
@stephen-riley
It totally did work until I put the code inside the lambda I'm passing to ContinueWith().
me-slove
@me-slove
actorselection is probably a reference. in which case you'd be back to the closure problem
Stephen Riley
@stephen-riley
I built the code first just using await httpClient.GetAsync()...
@me-slove , I've tried closing over it, too, and it still didn't work. Which is weird to me, cuz I figured if I'd closed over it, I'd get all the context linked to it and be fine.
me-slove
@me-slove
inside the same code block it should work though. that seems a little odd
Stephen Riley
@stephen-riley
Agreed, @me-slove , it is quite odd. I just re-tested that, still doesn't work.
var self = Self;
var context = Context;

httpClient.GetAsync(req.Url).ContinueWith(responseTask =>
{
    var mylogger = context.ActorSelection("/user/ConsoleLogger");
    var response = responseTask.Result;
    var duration = stopwatch.Elapsed.TotalMilliseconds;
    var msgResponse = new AkkaBlaster.Dto.WebResponse
    {
        StatusCode = response.StatusCode,
        Duration = duration
    };

    mylogger.Tell("message");
},
TaskContinuationOptions.AttachedToParent & TaskContinuationOptions.ExecuteSynchronously);
Onur Gumus
@OnurGumus
@stephen-riley can you actually try to resolve the selection by calling Resolve ?
Stephen Riley
@stephen-riley
The actor mylogger definitely receives the message, but it is from deadLetters, instead of from this httpclient actor.
@OnurGumus , I don't know about Resolve(), but I will try that!
Onur Gumus
@OnurGumus
ActorSelection returns a selection , not an actor ref. You can get an actorRef by calling Resolve on the Selection.
Stephen Riley
@stephen-riley
Do you mean ResolveOne()?
Onur Gumus
@OnurGumus
which may fail if no such actor found.
yes that one
Stephen Riley
@stephen-riley
k, let me try
Onur Gumus
@OnurGumus
I would also move the resolution outside of your lambda.
there is no need to resolve it there. You can resolve before.
me-slove
@me-slove
I haven't looked at the code for Context but what you are seeing for sure is that it is losing itself across the task boundary. It must be that it is derived instead of a variable
Stephen Riley
@stephen-riley
It must be that it is derived instead of a variable