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
Roger Johansson
@rogeralsing
Btw, should we roll our own serializer?
In fed up with existing ones that does not handle what we need
Bartosz Sypytkowski
@Horusiath
you mean, totally our own in the future or just custom converter for JSON.NET?
Kjellski
@kjellski
Have you had a look on fastjson? http://www.codeproject.com/Articles/159450/fastJSON
Bartosz Sypytkowski
@Horusiath
I think, that we could talk with James Newton King to borrow his F# discriminated union converter until the fixed version of JSON.NET will eventually came out
Aaron Stannard
@Aaronontheweb
@Horusiath good idea - want to reach out and ask?
Bartosz Sypytkowski
@Horusiath
ok
Roger Johansson
@rogeralsing
We used fast json in the beginning, but it uses a static context which makes things like serializing actorref, which needs to be bound to a system
Kjellski
@kjellski
@rogeralsing ah, I see... too bad, it's really impressive how good it worked in our context. And the speed is crazy too ;)
Bartosz Sypytkowski
@Horusiath
if we'd like to drop json.net for something else, I'd stand more for something like protobuf or thirft
Bartosz Sypytkowski
@Horusiath
@Aaronontheweb what about Helios documentation? If you wanna more help there, it's essential
Håkan Canberger
@HCanber
I managed to commit directly to our repo instead of sending a PR
Aaron Stannard
@Aaronontheweb
@Horusiath yeah, I really do need help on the Helios docs
Håkan Canberger
@HCanber
About to direct-commit a commit that reverts all those commits and then submit a PR
Aaron Stannard
@Aaronontheweb
@HCanber that should be fine
@Horusiath I've been totally swamped on Akka.NET stuff lately - I'm switching gears to Helios today so I can get Helios v1.4 out alongside Akka.NET 1.0
has all of the mono fixes @stefansedich wrote that will allow Akka.Remote to work properly on Mono
Håkan Canberger
@HCanber
So everything has been reverted. Sorry 'bout that.
Aaron Stannard
@Aaronontheweb
no worries @HCanber - happens to the best of us.
I had someone at MarkedUp accidentally delete the master branch of our core product instead of his personal master branch (he had commit access, since he was responsible for deployments)
thankfully our CI system also used git, so it was easy to restore :p
plus we all had local copies of it
yay for distributed source control!
Håkan Canberger
@HCanber
:smile:
Natan Vivo
@nvivo
@rogeralsing, @HCanber, out of curiosity, did you ever decide if #700 would remain merged for 1.0 or would become experimental? Since the api was frozen for 1.0, I was wondering what happened to that discussion. Did you reach any consensus?
Aaron Stannard
@Aaronontheweb
@nvivo we decided to go with @rogeralsing's solution and end all discussion on the subject
not interested in revisiting it until after 1.0 ships
Natan Vivo
@nvivo
ok
Yoann
@arthis
@horusiath thx for the answer
Aaron Stannard
@Aaronontheweb
hey guys, so there's been a lot of conversations about Petabridge's role in Akka.NET going forward. In light of what happened with FoundationDB and Apple last week, we thought we'd make it really, really damn clear what we intend to do: http://petabridge.com/blog/no-more-foundationdbs/
OSS all the way
Andrew Skotzko
@skotzko

ossfolife

jcwrequests
@jcwrequests
@Aaronontheweb @skotzko Nice post guys! :+1: :clap:
Andrew Skotzko
@skotzko
@jcwrequests thank you señor
jcwrequests
@jcwrequests
@skotzko No Problemo
Andrew Skotzko
@skotzko
situation really highlights the issues w/ closed source solutions
jcwrequests
@jcwrequests
Hey all I was talking with @Aaronontheweb about creating a screencast documenting doing a proper Pull Request from Akka point of view. I was thinking of doing examples this using Git Hub for windows, Git bash and SourceTree. If anyone is interested, since I know @Aaronontheweb has his plate full, to review a screencast script to ensure that I am not missing anything please let me know. My plan is to create a repo for the script , potential diagrams and slides for this project. It will definitely be an iterative process and I want to be as detailed as possible so any input would be welcome. Thanks,
Aaron Stannard
@Aaronontheweb
@jcwrequests I think it'd be a super good idea - will definitely help new contributors. And it's a best practice in general for Github OSS
I'm sure folks would be happy to review it once you have a draft up - I'll personally make time to check it out no problem
Arjen Smits
@Danthar
@jcwrequests that is a really great idea. I'm not an expert on pull-requests (never done one, never had to). But I am more then happy to provide feedback from a n00b perspective. Once the vid is up.
Arjen Smits
@Danthar

Is this really the correct way to do this?

 protected override void PreStart()
   {
      var producer = Context.System.GetExtension<DIExt>();
       childActor = Context.ActorOf(producer.Props("MyActor"));
      base.PreStart();
   }

Why cant I do this?

protected override void PreStart()
    {
        var producer = Context.System.GetExtension<DIExt>();
        childActor = Context.ActorOf(producer.Props<MyActor>());
        base.PreStart();
    }
Kjellski
@kjellski
I've just installed Akka.Remote, is it normal that it already pulls down Google Protobuf and pukes folders and license stuff into my project?
Roger Johansson
@rogeralsing
Blame nuget for that, akka remote has a ref to protobuf . So both nuget packages get installed
And protobuf package does that when installed
Arjen Smits
@Danthar
hmm funny, Just slammed head first into issue #706 Good to see its already registered as an issue. However I am unsure about what the status is now, since @Aaronontheweb opened it again.
Aaron Stannard
@Aaronontheweb
@Danthar I just haven't merged the code that resolves this issue in yet - was planning on doing that yesterday but ended up tackling some remoting issues instead
Arjen Smits
@Danthar
Ah like that. Ok. Once you merged that code, will the nuget packages be updated automatically or should I build from source?
Aaron Stannard
@Aaronontheweb
you'll need to build from source for now - we're going to do a bigger release next week that has all of the official nuget packages
Aaron Stannard
@Aaronontheweb
@smalldave can I pull in your remoting terminator changes?
Aaron Stannard
@Aaronontheweb
spent all day working in Mono on my dedicated Ubuntu hardware - can confirm that Helios now runs like a champ on it. Benchmarks aren't nearly as good compared to Windows but that'll come with some time as Mono starts to reap the benefits of the CLR being open source.