Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Activity
  • 19:34
    IgorFedchenko synchronize #3973
  • 17:53
    Aaronontheweb closed #3972
  • 17:53
    Aaronontheweb commented #3972
  • 17:53
    Aaronontheweb closed #3976
  • 17:53
    Aaronontheweb commented #3976
  • 17:40

    Aaronontheweb on dev

    cleaned up some samples to use … (compare)

  • 17:40
    Aaronontheweb closed #3975
  • 16:33
    IgorFedchenko synchronize #3973
  • 16:31
    IgorFedchenko synchronize #3973
  • 14:04
    wsvdyk opened #3976
  • Oct 14 21:02
    Aaronontheweb synchronize #3975
  • Oct 14 21:02
    Aaronontheweb opened #3975
  • Oct 14 20:11
    IgorFedchenko commented #3973
  • Oct 14 20:10
    IgorFedchenko synchronize #3973
  • Oct 14 20:06
    IgorFedchenko synchronize #3973
  • Oct 14 20:06
    IgorFedchenko synchronize #3973
  • Oct 14 19:42
    IgorFedchenko edited #3973
  • Oct 14 18:08
    Aaronontheweb commented #3937
  • Oct 14 17:27
    Aaronontheweb commented #90
  • Oct 14 17:26
    Aaronontheweb commented #90
Aaron Stannard
@Aaronontheweb
they're all optional anyway
Aaron Stannard
@Aaronontheweb
anyone understand why the NLog logger wouldn't work with the following configuration?
<?xml version="1.0" ?>
<nlog xmlns="http://www.nlog-project.org/schemas/NLog.xsd"
      xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
  <targets>
    <!--<target name="eventlog" xsi:type="EventLog" layout="${logger}: ${message}" source="Lighthouse" log="Application" />-->
    <target name="console" xsi:type="ColoredConsole" layout="${date:format=HH\:MM\:ss} ${logger} ${message}"></target>
  </targets>

  <rules>
    <!--<logger name="*" minlevel="Warn" writeTo="eventlog" />-->
    <logger name="*" minlevel="Info" writeTo="console" />
  </rules>
</nlog>
commented out the eventlog stuff, but not seeing anything appear on the console
cc @mmisztal1980
David Smith
@smalldave
is that in nlog.config
Aaron Stannard
@Aaronontheweb
yes
David Smith
@smalldave
i just spent a while cursing logging because I didn't have always copy set on nlog.config
Aaron Stannard
@Aaronontheweb
welp, that fixed it
David Smith
@smalldave
hope that saved you the time I wasted
Aaron Stannard
@Aaronontheweb
I am hilariously inept at using third party logging tools
David Smith
@smalldave
;)
Aaron Stannard
@Aaronontheweb
it's one of those things where I went so long without having to set one up myself that I became too afraid to ask :worried:
Bartosz Sypytkowski
@Horusiath
do you guys think that open plugins proposals with up for grabs labels have sense?
David Smith
@smalldave
problem is that app.config web.config copy automatically. you forget that you have to opt in for other files
Aaron Stannard
@Aaronontheweb
@Horusiath totally - I think it'd be really cool if someone decided to write some of the persistence plugins you proposed
David Smith
@smalldave
agreed. can't do any harm
Aaron Stannard
@Aaronontheweb
yeah, the worst that can happen is someone submits something that doesn't work and the pull request doesn't get accepted
Bartosz Sypytkowski
@Horusiath
I'm thinking about blog post being tutorial of how to roll your own persistence plugin
Aaron Stannard
@Aaronontheweb
I think thats a great idea too @Horusiath
Aaron Stannard
@Aaronontheweb
that's something I'm personally interestedin
Andrew Skotzko
@skotzko
that would be super cool
write away @Horusiath !
jcwrequests
@jcwrequests
@Horusiath I would second that.
jcwrequests
@jcwrequests
It's definitely something that would be worth it.. Here is some inspiration from the JVM side https://vaughnvernon.co/?p=986 using Postgres.
jcwrequests
@jcwrequests
@Aaronontheweb Is there some simple documentation say a diagram showing the basic hierarchy of the Akka internals and how they play together. I am still trying to find a good place within the code base for that IOC release strategy and getting hung up on the life cycle and the other responsibilities of the system.
jcwrequests
@jcwrequests
@Aaronontheweb I was just looking over on the JVM side and found this Stop Hook
After stopping an actor, its postStop hook is called, which may be used e.g. for deregistering this actor from other services. This hook is guaranteed to run after message queuing has been disabled for this actor, i.e. messages sent to a stopped actor will be redirected to the deadLetters of the ActorSystem.
Andrew Skotzko
@skotzko
@jcwrequests so you're looking for a good overview fo the lifecycle? we don't have everything documented AFAIK, but for life cycle specifically we did a good write up here : https://github.com/petabridge/akka-bootcamp/tree/master/src/Unit-1/lesson6
jcwrequests
@jcwrequests
Thanks @skotzko I will definitely check that out. Trying to figure it out strictly from the code base is not exactly easy.
Andrew Skotzko
@skotzko
hear ya. docs will improve soon.
jcwrequests
@jcwrequests
No problem. As I am learning new things I will definitely document through my blog.
Really you guys are doing an assume job!!!!
jcwrequests
@jcwrequests
@skotzko I just took a quick look. I see the part about the void PostStop() but that is something that needs to be implemented by the actor. What I am look for is more about the internals. So Props creates instances I need to have some hook to do releases of the actor created using my IOC contrib. All the someone should have to do is wire up the IOC container and then let Akka do the rest. Regardless the information is very helpful so thanks.
jcwrequests
@jcwrequests
@Aaronontheweb @skotzko I think within the ActorCell specifically private void FinishTerminate() might be able to call a release method on Props. In Fact I think Props should have a Release method or expose the IndirectActorProducer where having the Release method makes most sense. I believe that was what you were referring to the last time we chatted.
jcwrequests
@jcwrequests
@Aaronontheweb I think that will work I will prototype it the come up with a proposal.
jcwrequests
@jcwrequests
@Aaronontheweb @skotzko Do you think putting together a well commented gist be sufficient for a proposal or should I put together a full blown google doc and share it with the group?
Aaron Stannard
@Aaronontheweb
@jcwrequests I think a gist is a good start
you can also try this, which I've been in love with lately: https://dotnetfiddle.net/
Stefan Sedich
@stefansedich
@jcwrequests happy to help out on this if you need another pair of hands.
jcwrequests
@jcwrequests
@Aaronontheweb thanks for the link I will check it out. Today I was thinking that it actually may make a good blog post. Currently I am trying to keep a cadence of a new post every two weeks and right now I am a little off track and this would be the perfect thing to talk about since it's what my current focus is. @stefansedich thanks for offer I might take you up on it. I already have some preliminary thoughts down on paper which I know will work but what I am trying to do is minimize any impact to the core framework.
jcwrequests
@jcwrequests
@stefansedich it looks like from your LinkedIn Profile you do AutoFac which would definitely come in handy since my IOC of choice is Castle WIndsor. Since my IOC contrib is being reworked it may be worth while to also find a way to validate the container to ensure that all registred actors are using the proper life cycle, like transient. I know it's something that is fairly easy to do in Castle but I am not sure about the other IOC containers. It's not something that is absolutely necessary but it help keep users on the happy path.
Stefan Sedich
@stefansedich
yeah happy to help with the autofac stuff.
jcwrequests
@jcwrequests
@stefansedich Is it it already Monday evening in Australia?
Stefan Sedich
@stefansedich
10am in the morning :)
with autofac the props will need to work a bit differently I think
we should resolve an Owned<T>
and then later dispose that owned so that we release things properly.
Autofac container does not have anything like a release method.
or create a LifetimeScope and keep track of that inside the props, then when you call Props.Dispose() dispose that LifetimeScope
jcwrequests
@jcwrequests
Sounds good to me. I am basing this on a great post that I read by the author of Dependency Injection for .Net Mark Seemann.