Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Activity
  • 14:26
    nagytech commented #3954
  • 11:18
    nagytech edited #4089
  • 11:17
    nagytech opened #4089
  • 11:00
    nagytech commented #4083
  • 08:34
    jiyeongj commented #4083
  • 08:33
    jiyeongj commented #4083
  • 08:33
    jiyeongj commented #4083
  • 07:57

    dependabot-preview[bot] on nuget

    (compare)

  • 07:57

    dependabot-preview[bot] on dev

    Bump MongoDB.Driver from 2.9.1 … (compare)

  • 07:57
    dependabot-preview[bot] closed #104
  • 07:52
    dependabot-preview[bot] synchronize #104
  • 07:52

    dependabot-preview[bot] on nuget

    Bump MongoDB.Driver from 2.9.1 … (compare)

  • 07:52
    dependabot-preview[bot] edited #104
  • 07:51
    dependabot-preview[bot] edited #104
  • 07:51
    dependabot-preview[bot] edited #104
  • 07:51
    Aaronontheweb commented #104
  • 07:43

    dependabot-preview[bot] on nuget

    (compare)

  • 07:43

    dependabot-preview[bot] on dev

    Bump Microsoft.NET.Test.Sdk fro… (compare)

  • 07:43
    dependabot-preview[bot] closed #102
  • 07:43
    Aaronontheweb commented #102
Aaron Stannard
@Aaronontheweb
;)
Arjen Smits
@Danthar
lol
Ow I ran into something else thats not so obvious at first
(let me create a quick gist to illustrate)
Arjen Smits
@Danthar
 Receive<WorkComplete>(_ => {
      //this never gets called, unless..
   });
never gets called. because the worker.tell(new StartWorkFor()) does not have a Sender reference
this is because the local actor context was not captured/ closed over
so you need to fix that by doing this:
 worker.Tell(new StartWorkFor(), Self); 
Aaron Stannard
@Aaronontheweb
that makes sense
Arjen Smits
@Danthar
its obvious for me, Because I know how Akka works. But its not so obvious from a newbie perspective
so maybe this should be something for the docs
Aaron Stannard
@Aaronontheweb
yeah, this is a bit of an abstract concept and one of the reasons why I want to burn async / await with fire
Arjen Smits
@Danthar
hahaha
Aaron Stannard
@Aaronontheweb
closures are a fact of life for asynchronous programming and this is an instance when it's unavoidable
have to close over the part the context you need to set up the next call inside a continuation
PipeTo and TPL methods make it explicit
async and await just silently fails
_<
Arjen Smits
@Danthar
But in this case. the subscription isn't async. Its just a closure/anonymous method func.
Aaron Stannard
@Aaronontheweb
guess that emojii doesn't work
yeah, you're right
Arjen Smits
@Danthar
i could do rabbitbus.SubscribeAsync
Aaron Stannard
@Aaronontheweb
that's something we're just going to have to educate people on - I make a point of doing that in Akka.NET bootcamp
Arjen Smits
@Danthar
then it would interpret the func im passing, as a Task
:nods:
I have hold off on doing async await stuff in the example I just displayed. Due to the current bugs with Akka
All kinds of wierd stuff happens once I do that lol
Aaron Stannard
@Aaronontheweb
PipeTo is your friend
just sayin
Arjen Smits
@Danthar
PipeTo marshalls it back to the original actor context?
Aaron Stannard
@Aaronontheweb
nope - turns the result of a task into a new message
it's just an extension method
Arjen Smits
@Danthar
owyeah. I know that
just realized. isn't it 02:00 over at your place now?
Aaron Stannard
@Aaronontheweb
midnight - west coast of the US
Arjen Smits
@Danthar
ah, so late. but not that late :P
Anthony Brown
@bruinbrown
@Aaronontheweb just given the hanselminutes a listen, really good, given me some nice analogies to help explain it better
Natan Vivo
@nvivo
Suppose I want to customize the default dispatcher, can I do this?
akka.actor.default-dispatcher {
    throughput = 50
    throughput-deadline-time = 1s
}
Roger Johansson
@rogeralsing
Yes
Natan Vivo
@nvivo
thanks
Roger Johansson
@rogeralsing
Whichever occurs first , count or deadline will exit the mailbox run
Arjen Smits
@Danthar
Hmm
Can I pass an ActorSelection instance around in messages ?
myActor.Tell(new MyMessage() { childWorker = Context.ActorSelection("myactor") });
So like that?
reason I am asking is because Im using a specific actor to process certain database actions. And I want to...
ok nevermind
Natan Vivo
@nvivo
I think you can, since you can pass ActorRefs
Arjen Smits
@Danthar
realised using a concistent hashing router would solve my problems