by

Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Activity
  • 16:37
    to11mtm commented #4563
  • 16:34
    to11mtm commented #4563
  • Sep 25 07:59
    ingted commented #4570
  • Sep 25 07:57
    ingted commented #4570
  • Sep 25 07:54
    ingted commented #4570
  • Sep 25 06:10
    ismaelhamed commented #4570
  • Sep 24 22:46
    nagytech commented #4570
  • Sep 24 14:18
    ingted commented #4570
  • Sep 24 10:40
    ingted edited #4570
  • Sep 24 10:39
    ingted edited #4570
  • Sep 24 10:36
    ingted edited #4570
  • Sep 24 10:33
    ingted opened #4570
  • Sep 17 17:14
    briansain commented #4567
  • Sep 17 16:59
    briansain synchronize #4568
  • Sep 17 16:27
    VaclavK closed #51
  • Sep 17 16:27
    VaclavK closed #50
  • Sep 15 14:57
    BartHuls closed #4569
  • Sep 15 14:18
    Aaronontheweb commented #4563
  • Sep 15 13:53
    Zetanova commented #4563
  • Sep 15 13:41
    Aaronontheweb commented #4563
Roger Johansson
@rogeralsing
There is an overload of Receive that takes an Func<TMessage,Task> , if you use that method, we apply the actor task scheduler and tasks will be scheduled to run inside the actor context
Or. you simply copy Self to self .. var self = Self before invoking the tasks.
@Aaronontheweb fixed one such bug in persistence in his latest dispatcher PR
you only need the Self ref there, right? or do you need to set actor state?
Bartosz Sypytkowski
@Horusiath
I've seen that trick once in canonical akka source code
hopefully it will be enough
Bartosz Sypytkowski
@Horusiath
worked :)
Roger Johansson
@rogeralsing
:+1:
@HCanber @Aaronontheweb which PR do we merge first? which one results in the least amount of re-work? as I take it that they will both break eachother
Roger Johansson
@rogeralsing
@/all should we really have the Wiki issues mixed with the framework issues on the main repo? the wiki pages are part of the main repo, but imo, it gets a bit messy, no?
Aaron Stannard
@Aaronontheweb
well the Chinese government is certainly giving Github and our build server a hard time today http://motherboard.vice.com/read/did-china-just-launch-a-cyber-attack-on-github
poor old TeamCity can't fetch its latest from Version Control :(
Stefan Sedich
@stefansedich
lol that is crazy @Aaronontheweb
David Smith
@smalldave
@Aaronontheweb I'll take a look at remotingterminator unless you plan to spend time on it. i think I've sorted cluster shutdown but still having issues when bringing a node up using the same port as an old node.
Aaron Stannard
@Aaronontheweb
@smalldave go for it - we're just about code complete for the v1.0 release and I'm going to be spending the next few days integrating @stefansedich's Mono fixes into a new release of Helios as part of Akka.NET 1.0
so we can ship with Mono support for Akka.Remote right out of the box
so if you can squeak the remoting terminator in over the next week that would be wonderful
I'll assign the issue to you
@/all if you're interested in taking your first step towards contributing to Akka.NET, here's a pretty straightforward issue you can get started with: akkadotnet/akka.net#765
Aaron Stannard
@Aaronontheweb
ok, time to break the codebase and do all of the big merges for V1.0 :)
(hopefully it doesn't actually break the code base, but you know - jokes and stuff)
Aaron Stannard
@Aaronontheweb
almost done regression testing @HCanber's big PR with mine... looking good so far
XUnit ate shit but what's new?
Aaron Stannard
@Aaronontheweb
cool, multinodespecs passed
good to go - let's merge it in
Roger Johansson
@rogeralsing
Go go :)
Aaron Stannard
@Aaronontheweb
Gonna let the build server do it's thing
then we'll merge it in
these two PRs combined should close out like 6-7 issues
not too shabby
Roger Johansson
@rogeralsing
The mofo that invented daylight savings should be dug up and killed again, Im jetlagged wo traveling...
Aaron Stannard
@Aaronontheweb
Kaiser Willhem of World War I Germany
is the dude you have to thank
wanted to save on fuel for his supply lines :p
but yeah, I felt the same way when we had ours two weeks ago
brutal
@rogeralsing I'm going to write up a blog post today announcing that we're code complete for V1 - we'll still accept PRs for bug fixes and for stuff that's not going into V1 (i.e. Akka.Persistence or Akka.Cluster changes), but otherwise the public APIs are now frozen
and to expect the release to happen sometime next week
(after we do docs and around of Mono QA)
sound right to you?
Roger Johansson
@rogeralsing
Yepp
Aaron Stannard
@Aaronontheweb
cool
tomorrow I start work on the release notes
which will be a beast :\
Roger Johansson
@rogeralsing
This is epic :)
Aaron Stannard
@Aaronontheweb
this is big achievement for Akka.NET and its community of contributors and users
over a year in the making
we'll be sure to celebrate once this thing hits NuGet next week
Aaron Stannard
@Aaronontheweb
so the final tally of things needed for V1