Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Activity
  • 11:49
    IgorFedchenko commented #4085
  • 10:31
    IgorFedchenko commented #4085
  • 08:36
    IgorFedchenko commented #4085
  • Dec 06 20:57
    IgorFedchenko commented #4085
  • Dec 06 20:32
    IgorFedchenko commented #4085
  • Dec 06 20:01
    IgorFedchenko commented #4085
  • Dec 06 19:55
    IgorFedchenko commented #4085
  • Dec 06 16:22
    Aaronontheweb labeled #3997
  • Dec 06 16:22
    Aaronontheweb closed #3997
  • Dec 06 16:20
    IgorFedchenko commented #3997
  • Dec 06 16:08
    IgorFedchenko commented #4085
  • Dec 06 15:50
    Aaronontheweb assigned #4085
  • Dec 06 15:50
    Aaronontheweb labeled #4085
  • Dec 06 15:50
    Aaronontheweb labeled #4085
  • Dec 06 15:49
    Aaronontheweb closed #4032
  • Dec 06 14:58
    IgorFedchenko commented #4032
  • Dec 06 14:57
    IgorFedchenko opened #4085
  • Dec 05 17:21
    Aaronontheweb synchronize #4079
  • Dec 05 17:20
    Aaronontheweb labeled #4084
  • Dec 05 17:20
    Aaronontheweb labeled #4084
Graham Ambrose
@gambrose
@DamianReeves you can set an IgnoreMessages function to ignore any messages that you are not interested in, then ExpectMsg the message you want. This is what I do but... there maybe a better way.
Nick Chamberlain
@heynickc
@DamianReeves FishForMessage is also a viable option:
[Fact]
public void Expect_message_after_a_few()
{
    var actor = Sys.ActorOf(Props.Create(() => new EchoActor()));
    var probe = CreateTestProbe();
    actor.Tell("Yo!", probe.Ref);
    actor.Tell("Hey!", probe.Ref);
    actor.Tell("Wasup!", probe.Ref);
    actor.Tell("Hello!", probe.Ref);
    actor.Tell("Nevermind...", probe.Ref);

    probe.FishForMessage(msg => (string) msg == "Nevermind...");
}
Weston
@ronnyek
so I am interested in having akka.net handle tcp listening, taking the inbound messages and treating them as reactive streams
is the examples with the telnet listener technically akka.io stuff?
Bartosz Sypytkowski
@Horusiath
@ronnyek there's a simple example which uses akka.io actors. But once we fix everything related to akkadotnet/akka.net#2405 I think, that streams will be a much better approach
Weston
@ronnyek
will streams be able to listen on tcp or websockets or anything like that?
I thought streams solved different problems
any eta on 1.2?
months
ballpark
weeks
quarters =)
Deniz İrgin
@Blind-Striker
or ... When it’s done :P
Weston
@ronnyek
I realize its done when its done, but I dont know if I need to just wait for that because its around the corner
or if its a long ways off I need to investigate other stuffs
Ricky Blankenaufulland
@ZoolWay
Hi! Wanted to hear if you have situation where you need a class/recordtype which is mutating (changing state) and nearly the same class as immutable to send it through Akka messages. If I encounter this, is it a code smell, an anti-pattern? If not, how do you name both? Customer and CustomerMutating? CustomerImmutable and Customer? CustomerFrozenand CustomerState?
Deniz İrgin
@Blind-Striker
I just quoted from Blizzard :) we have similar issue too and waiting for 1.2
@ronnyek
Bartosz Sypytkowski
@Horusiath
ETA v1.2 was 2 days ago ;)
Aaron Stannard
@Aaronontheweb
@Horusiath are we still waiting on NuGet support for that? cc @Silv3rcircl3
Bartosz Sypytkowski
@Horusiath
@ronnyek Akka.Streams will expose listener interface
basically TCP connection handler will be represented as source/sink for the stream
Dmitri Pavlenkov
@dpavlenkov
@ZoolWay I would append Message to anything immutable and sendable
Ricky Blankenaufulland
@ZoolWay
@dpavlenkov You mean like an audit of changes? Feels like a bit of overkill if I just have user objects and their presence changes during the day.
Dmitri Pavlenkov
@dpavlenkov
The pattern is for services to own objects and to modify them exclusively, and to communicate through messages, even changes to them.
Or copy, I guess
Ricky Blankenaufulland
@ZoolWay
Hm, to replace my cached immutable Customer with a new immutable Customer instance where the change is reflected?
Weston
@ronnyek
@Horusiath so soonish
Dmitri Pavlenkov
@dpavlenkov
@ZoolWay yeah, much safer. Models are really messages
Ricky Blankenaufulland
@ZoolWay
Thanks for sharing. It seems unconventional but I feel there are some good advantages in this approach. I'll try out
Alan Schrank
@alanschrank
[
Jeff Pang
@jeff-pang
hi, i am new to akka.net, so a few things I want to try out not sure if you guys have any idea on.
  1. I understand there are no consensus systems built into Akka, so is there any library or systems I can explore?
  2. I am assuming no for the preceding qns (but I could be wrong), so that leaves me with implementing my own, so do I write my own heartbeat or is there a way to leverage akka's heartbeat in akka.remote
Arsene
@Tochemey
Hello Geeks. Please how far with the AkkaStream?
Any tentative date?
Marc Piechura
@marcpiechura
@Tochemey Reactive.Streams was RTM-ed yesterday so we will upgrade our version and also release Akka.Streams as stable with 1.2
Arsene
@Tochemey
@Silv3rcircl3 Beautiful
@Silv3rcircl3 Can I use the RTM in production? also do you guys have some samples that help someone get started with the implementation of Network based protocol?
Marc Piechura
@marcpiechura
Yup, it's already in production in some other projects. I think there is a example in the cookbook in the docs
Arsene
@Tochemey
Ok cool
Franky Ostyn
@FOstyn

Hi all,
a NLog question: with NLog is it possible to define 2 or more different logfiles.
<rules>
<logger name="AkkaLog" minlevel="Debug" writeTo="logfile1" />
<logger name="myLogFile" minlevel="Debug" writeTo="logfile2" />
</rules>

Using the same config file for Akka doesn't work, nothing is logged from Akka, I think Akka expects the name = "" like:
<rules>
<logger name="
" minlevel="Debug" writeTo="logfile1" />
</rules>

Is it possible to define in HOCON the name of the logfile for Akka ?

--> No one knows how to define a specific Akka.NET logfile instead of the common used "*" with NLog ?

Arjen Smits
@Danthar
@FOstyn logger config is generally outside of akka.
meaing you can simply define different log files in nlog. And target them as you would normally do
only thing is, not sure how you that works with nlog, but you might have to go beyond the logger abstraction akka.net offers
Franky Ostyn
@FOstyn
Outside of Akka ? When using the Akka.Logger.Nlog you have to define a NLog.config, that's for me not 'outside of Akka'.
The NLog-Akka problem is that you must define a logger name= "<multiply-symbol>" for Akka, otherwise nothing will be logged for Akka.
This is annoying if you must write specific log data (with NLog) to another file and only to that file.
Because NLog writes always all data to that "<multiply-symbol>" log file it's all mixed up in that logfile.
It would be better if we could define a specific log file for Akka, that was the question. Is this possible and if so, can that be defined in HOCON ?
Damian Reeves
@DamianReeves
I'm trying to test an EventStream subscription in a TestKit test however I never get the message from the EventStream despite being subscribed
Damian Reeves
@DamianReeves
Are there any gotchas when testing EventStream?
Arjen Smits
@Danthar
@FOstyn Ah, i misunderstood then. NLog does not allow you to target different logging sinks ? Most logging frameworks allow you to write logs to a different sink, based on the 'context' where the context being the namespace or type where the logging is coming from.
I can imagine NLog allows similar behavior. But like i said earlier. I might have to go beyond the default logging abstraction akka.net offers. So in other words. Instead of using Context.GetLogger() to get the logging abstraction, you would have to call NLog directly.
Franky Ostyn
@FOstyn
@Danthar
thanks for your input, but maybe I'm not clear enough.
I know that I can use the NLog directly and that works, but that's not the point.
With NLog you can easily define more targets/rules. But if you define a 'common' target in NLog (with the <multiply-symbol>), NLog will write all log data from ANY target to that file.
And with Akka: if you want to use NLog with the Akka.NET system, you must define such a 'common' file name (with the <multiply-symbol>).
You can't use a dedicated file name for Akka only (which I would like to do). If you don't define such a 'common' file, Akka won't log anything.
What I have now, is a NLog.config file with 3 targets and one of them is such a 'common' file for Akka. The result is that all the logging data of the other 2 targets are also written to that Akka log file. And that's what I don't want.
Thanks for your time.
Arjen Smits
@Danthar
@FOstyn I created a quick test app with the nlog logger