Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Activity
  • 14:24
    dependabot-preview[bot] synchronize #4021
  • 14:24
    dependabot-preview[bot] synchronize #4046
  • 14:24
    dependabot-preview[bot] synchronize #4050
  • 14:24

    dependabot-preview[bot] on nuget

    Bump FSharp.Core from 4.5.0 to … (compare)

  • 14:24

    dependabot-preview[bot] on nuget

    Bump Mono.Cecil from 0.9.6.4 to… (compare)

  • 14:24

    dependabot-preview[bot] on nuget

    Bump ApprovalUtilities from 3.0… (compare)

  • 14:24
    dependabot-preview[bot] synchronize #4051
  • 14:24

    dependabot-preview[bot] on nuget

    Bump ApprovalTests from 3.0.10 … (compare)

  • 14:24
    dependabot-preview[bot] edited #4021
  • 14:24
    dependabot-preview[bot] edited #4046
  • 14:24
    dependabot-preview[bot] edited #4050
  • 14:24

    dependabot-preview[bot] on nuget

    Bump ApiApprover from 3.0.1 to … (compare)

  • 14:24
    dependabot-preview[bot] synchronize #3989
  • 14:24
    dependabot-preview[bot] edited #4051
  • 14:24
    dependabot-preview[bot] synchronize #3986
  • 14:24

    dependabot-preview[bot] on nuget

    Bump NUnit from 3.6.1 to 3.12.0… (compare)

  • 14:24
    dependabot-preview[bot] synchronize #3985
  • 14:24

    dependabot-preview[bot] on nuget

    Bump FsCheck.Xunit from 2.9.0 t… (compare)

  • 14:24
    dependabot-preview[bot] edited #3989
  • 14:24
    dependabot-preview[bot] edited #3986
Stefan Sedich
@stefansedich
oh hi @liammclennan :D
from what I can tell the EventStream is the only implementation of the EventBus
Liam McLennan
@liammclennan
Figured. I was trying to put pub/sub between actors so the dependencies are not so fixed.
Roger Johansson
@rogeralsing
@liammclennan yes the event bus docs are completely lacking atm, I'll try to create some examples for it this weekend, its a great feature that dont get much exposure atm in akka.net
But in short, there is a baseclass one can inherit and override methods to categorize messages
Stefan Sedich
@stefansedich
not yet @rogeralsing will do so tonight.
@rogeralsing do you think implementing things like LookupEventBus and SubchannelEventBus are useful?
Aaron Stannard
@Aaronontheweb
@rogeralsing listening to it now
Stefan Sedich
@stefansedich
LOL
Aaron Stannard
@Aaronontheweb
;)
Stefan Sedich
@stefansedich
didn't you record it :D
Aaron Stannard
@Aaronontheweb
I can't get enough of hearing myself talk
Stefan Sedich
@stefansedich
haha
you and me both
Stefan Sedich
@stefansedich
I often listen to your voice at night right before going to sleep

notcreepy

Aaron Stannard
@Aaronontheweb
LOL
Aaron Stannard
@Aaronontheweb
just finished
I give myself a 10/10 A+ good job
errr :partly_sunny:
just kidding - I thought it turned out pretty well.I
I
I'm just jealous that Scott came up with all of the good analogies first :p
Arjen Smits
@Danthar
@rogeralsing Btw async await is broken in nuget 1.0 package
Aaron Stannard
@Aaronontheweb
yeah we've put a lot of fixes in for that since 1.0
Arjen Smits
@Danthar
I feel like your a broken record ^^
Aaron Stannard
@Aaronontheweb
#886 is the last big one
lol
Arjen Smits
@Danthar
@Aaronontheweb Yup i know, Found one myself.
Aaron Stannard
@Aaronontheweb
maybe it's by design so people start using PipeTo
;)
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