Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Activity
  • Dec 11 23:52
    scptre commented #4082
  • Dec 11 14:26
    nagytech commented #3954
  • Dec 11 11:18
    nagytech edited #4089
  • Dec 11 11:17
    nagytech opened #4089
  • Dec 11 11:00
    nagytech commented #4083
  • Dec 11 08:34
    jiyeongj commented #4083
  • Dec 11 08:33
    jiyeongj commented #4083
  • Dec 11 08:33
    jiyeongj commented #4083
  • Dec 11 07:57

    dependabot-preview[bot] on nuget

    (compare)

  • Dec 11 07:57

    dependabot-preview[bot] on dev

    Bump MongoDB.Driver from 2.9.1 … (compare)

  • Dec 11 07:57
    dependabot-preview[bot] closed #104
  • Dec 11 07:52
    dependabot-preview[bot] synchronize #104
  • Dec 11 07:52

    dependabot-preview[bot] on nuget

    Bump MongoDB.Driver from 2.9.1 … (compare)

  • Dec 11 07:52
    dependabot-preview[bot] edited #104
  • Dec 11 07:51
    dependabot-preview[bot] edited #104
  • Dec 11 07:51
    dependabot-preview[bot] edited #104
  • Dec 11 07:51
    Aaronontheweb commented #104
  • Dec 11 07:43

    dependabot-preview[bot] on nuget

    (compare)

  • Dec 11 07:43

    dependabot-preview[bot] on dev

    Bump Microsoft.NET.Test.Sdk fro… (compare)

  • Dec 11 07:43
    dependabot-preview[bot] closed #102
Aaron Stannard
@Aaronontheweb
@smalldave newbie Topshelf question for you - is there any specific convention I need to follow when setting up commandline arguments?
like /mycommand {commandvalue}
David Smith
@smalldave
why do you want them for a service? when it's being installed?
Aaron Stannard
@Aaronontheweb
for when it's being installed
basically someone can pass in the IP, port number, and a debug flag that the service will use when it runs
David Smith
@smalldave
ok and you store it locally somewhere?
Aaron Stannard
@Aaronontheweb
Ideally I'd like it to be passed in each time in the service runs
David Smith
@smalldave
can't say I've done that before. usually just use config file
Aaron Stannard
@Aaronontheweb
as part of the service's command line
David Smith
@smalldave
ah. no idea if you can do that. I'm guessing not though
Aaron Stannard
@Aaronontheweb
actually, I guess this is mostly just for debugging
because the way this stuff really gets set is via .config
using the usual HOCON configuration stuff
David Smith
@smalldave
answer is I don't know. i guess topshelf will complain that it doesn't understand the parameters as it is trying to interpret them
should have read that properly. apparently doesn't work
Aaron Stannard
@Aaronontheweb
eh, in that case I'll just strip the commandline arguments out
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.