Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Activity
  • Sep 20 23:30

    Aaronontheweb on dev

    added ability to support custom… (compare)

  • Sep 20 23:30
    Aaronontheweb closed #3923
  • Sep 20 23:30
    Aaronontheweb closed #3861
  • Sep 20 23:26
    Aaronontheweb opened #3923
  • Sep 20 23:01
    Aaronontheweb commented #3922
  • Sep 20 22:59
    Aaronontheweb closed #3890
  • Sep 20 22:59
    Aaronontheweb commented #3890
  • Sep 20 22:58
    Aaronontheweb synchronize #3922
  • Sep 20 22:58
    Aaronontheweb opened #3922
  • Sep 20 22:21
    Aaronontheweb commented #3905
  • Sep 20 22:21

    Aaronontheweb on dev

    Fixed Akka.Remote.ResendUnfulfi… (compare)

  • Sep 20 22:21
    Aaronontheweb closed #3914
  • Sep 20 22:21
    Aaronontheweb closed #3905
  • Sep 20 21:07
    Aaronontheweb milestoned #3921
  • Sep 20 21:07
    Aaronontheweb labeled #3921
  • Sep 20 21:07
    Aaronontheweb labeled #3921
  • Sep 20 20:53
    spankr opened #3921
  • Sep 20 18:52
    ismaelhamed commented #3811
  • Sep 20 17:42
    Aaronontheweb commented #3879
  • Sep 20 17:39
    Aaronontheweb commented #3887
Aaron Stannard
@Aaronontheweb
Properties/AssemblyInfo.cs inside the core Akka.NET project will show you where we did that in a number of areas
that'll give your assembly access to the MonotonicClock even though it's internal
Anthony Brown
@bruinbrown
@Aaronontheweb cool, I'll take that approach
Aaron Stannard
@Aaronontheweb
@billyxing @creepone we'll make sure that #1087 gets done - it's important to make the reason for those messages clearer. But in the meantime, remote deathwatch should work fine. Could you show me a gist where you're setting it up and handling it?
@cpx taking a look at your PR now
going to see if I can replicate that error
yep, repro'd it
Aaron Stannard
@Aaronontheweb
looks like the message is being sent twice...
interessant
Aaron Stannard
@Aaronontheweb
ha! I figured it out
@cpx so one of the things we do inside Akka.Remote when we first create an association is we put all non-system messages into a buffer, queued for delivery after the association opens
in the event that some of those buffered messages fail delivery, we schedule a backoff + retry
so the reason why we're seeing two OversizedPayloadExceptions is because of the retry
this is the culprit:
private void Writing(object message)
        {
            if (message is EndpointManager.Send)
            {
                var s = message as EndpointManager.Send;
                if (!WriteSend(s)) //returns false on oversized payload
                {
                    if (s.Seq == null) EnqueueInBuffer(s);
                    ScheduleBackoffTimer();
                    Context.Become(Buffering);
                }
            }
inside Endpoint.cs
Aaron Stannard
@Aaronontheweb
ok, this is an easy fix actually
I'll post a comment on the diff
John Haigh
@haighis
@Aaronontheweb akkadotnet/HOCON#11
Aaron Stannard
@Aaronontheweb
thanks @haighis
working on syncing all of my repos to Travis now
I figure it'd be fun to switch things up a bit a give Travis a try on this repo
John Haigh
@haighis
@Aaronontheweb make sure you specify the solution name correctly.. I didn't ...can you merge this PR akkadotnet/HOCON#25
Suhas Chatekar
@schatekar
@Aaronontheweb I added some questions on the PR for the multinode spec you ported. This is more for my understanding of how the spec works
I am not sure if it was appropriate to add comments on the PR though
Tomas Vana
@creepone
blob
@Aaronontheweb I boiled it down to this gist. I start 2 instances of this app, reconfiguring each to point to the other one. If I kill one of them and wait for ca. 2 seconds, the first one does get the Terminated message and Peer terminated is printed. However, if I'm too fast to restart the killed instance running on the same port, the first one gets confused, spits out the errors above and the Terminated message is not received.
Roger Johansson
@rogeralsing
@creepone that sounds like an UID issue, the new system should not get the same UID as the previous one and the cluster should not think they are the same
Tomas Vana
@creepone
@Aaronontheweb I just figured that adding AwaitTermination after the Shutdown call fixes it both in 1.0.4 and 1.0.5 if I stop it gracefully. When killing it hard, even in 1.0.5 the behavior is same though. Of course when under my control I can try to gracefully close it down, but what if it crashes on me and gets restarted automatically ?
@rogeralsing That sounds plausible. Is there any way to confirm (find out what the UIDs are) ?
Roger Johansson
@rogeralsing
what bits are you running? nuget or dev branch?
Tomas Vana
@creepone
I tried both nuget and 1.0.5.69-beta from the MyGet feed.
Bartosz Sypytkowski
@Horusiath
@Aaronontheweb why did you put all of the spec porting tasks in a separate issues each? This feels a little messy for me
also guys, what is the state of the Paket in akka.net?
Roger Johansson
@rogeralsing
@Horusiath I think the individual issues are good, easier for new contrbutors to pick just one and complete that one
also, IMO we should have a meeting regarding Paket and Migrant, not stuff we can decide too lightly
Bartosz Sypytkowski
@Horusiath
@rogeralsing I have a hard time in my work right now, I couldn't manage enough time to test Migrant myself, my concern is still performance comparison
billyxing
@billyxing
@Aaronontheweb here is the gist where I am setting it up and handling terminated message. gist
Steven van der Merwe
@SaberZA
Hey all, I'm trying to assess the use of Akka.Net in production. Currently, I'm looking at some sort of DDD approach with async / non-blocking IO operations for all my logic components, and I just feel that Actors is the space that I need to be in right now. I am also likely to have scaling problems, so the actor model seems even more viable. Is the current Akka.Net version stable enough for production?
Roger Johansson
@rogeralsing
@Horusiath Ill do some benchmark tests. My guess is that network will be a larger overhead than serialization
They do use reflection emit heavily so i think they have perf under control. But Ill check it out
Bartosz Sypytkowski
@Horusiath
@SaberZA we already have a guys running it on production
Geert Van Laethem
@GeertVL
What is the best time of the day to ask for new issues to work on?
Key contributors are not online whole day I suppose.
Roger Johansson
@rogeralsing
I think we are, some in the US and some on Europe.
Geert Van Laethem
@GeertVL
@rogeralsing can you give me a new issue or thing I can work on to help?
Roger Johansson
@rogeralsing
Im out right now, check any "up for grabs" or "help wanted" issue and just add a comment to the one you want
Geert Van Laethem
@GeertVL
@rogeralsing ok I will do that.
Maciek Misztal
@mmisztal1980
Hey guys, I'm writing a simple tool to stress-test one of our apps, I'd apreciate a hint on how to measure the execution time of the HttpClient and attach it via PipeTo? (currently I'm piping the HttpResponseMessage :worried:
using (var client = new HttpClient())
            {
                var request = new HttpRequestMessage(msg.HttpMethod, msg.Uri);

                client
                    .SendAsync(request)
                    .PipeTo(Self);
            }