akkadotnet/akka.net

Port of Akka actors for .NET

AnchishkinAlex

@AnchishkinAlex

@Horusiath does it mean asking of actor for EnumType is non-standard? For example, is it better to create Message class with Enum field?

Bartosz Sypytkowski

@Horusiath

@AnchishkinAlex I mean, you may try to use custom serializer for the enum type. Usually actors exchange more complex messages, afaik enum field in complex object should be deserialized correctly

AnchishkinAlex

@AnchishkinAlex

@Horusiath ok. I asked it because this problem occurs only with remote actor. Actors from one actor system can return enum type without exception. So I need explore near custom deserialization and serialization?

Bartosz Sypytkowski

@Horusiath

yes, messages exchanged between actors on the same node are not serialized.

AnchishkinAlex

@AnchishkinAlex

@Horusiath thanks! The last question: has Akka.Cluster some implementations for serialization? Does it make sense to realize Akka.Cluster only for fixing it?

Bartosz Sypytkowski

@Horusiath

@AnchishkinAlex I don't quite get your question.

AnchishkinAlex

@AnchishkinAlex

@Horusiath I'm sorry. If I'll make connection between actors through Akka.Cluster this problem can be fixed automatically? Or it needs custom serializer anyway?

Bartosz Sypytkowski

@Horusiath

Akka.Cluster is a layer on top of Akka.Remote - it doesn't replace transport

AnchishkinAlex

@AnchishkinAlex

Ok. Thanks a lot! All the best!

Bartosz Sypytkowski

@Horusiath

no problem ;)

Vagif Abilov

@object

Thanks @Horusiath

Bart de Boer

@boekabart

I had this idea today that would greatly help debugging Akka applications (actually, unit tests) - a way to render all the interactions between actors as a sort of 'sequence diagram' . But in order to do this, I need some kind of hook that tells me about each message being Telled. IIRC Monitoring does something like it - but is there a generic way to hook in somewhere in order to get the data I'm looking for?

Bart de Boer

@boekabart

Hook into Dispatcher somehow?

Aaron Stannard

@Aaronontheweb

the ActorCell or mailbox maybe

ActorCell has the best information probably

if not there then overriding the AroundReceive base method

on your actors

Bart de Boer

@boekabart

The thing with AroundReceive is that... it's actually the moment of telling that's interesting as well

most interesting and consistent, as multiple Tells will always be in the right order then.

But Dispatcher can't have the hook as it handles entire mailboxes, and Monitoring , well, requires changes to each actor as well...

Going to look at Cell

Andrew Young

@ayoung

as far as you guys know, compatibility between nodes running in .NET Framework and .NET Core isn't a problem, right?

Cluster nodes, that is.

Bart de Boer

@boekabart

@ayoung IIRC it is not supported at all (serialization issues with at least one of the serializers)

Arjen Smits

@Danthar

@ayoung @boekabart Im not aware of any issues? If you use the same serializer on each side, it should not be an issue. Best approach would be to use protobuff all the way through.

/cc @alexvaluyskiy ?

Roman Golenok

@shersh

Guys, is Akka.IO ready for production?
I still see TBD in documantation for classes.

Alex Valuyskiy

@alexvaluyskiy

@shersh yes, it is ready. TBD is related only for XML Documentation, not for the API itself

Paweł Bańka

@pmbanka

Hi, I have a question related to Stash. I don't understand this piece of docs:

The IWithUnboundedStash interface implementation of PreRestart will call UnstashAll(), which is usually the desired behavior.

(http://getakka.net/articles/actors/receive-actor-api.html#stash) Does this happen automagically when I implementIWithUnboundedStash on my actor? Where is this logic defined? I can't find it...

The closest candidate seems to be this https://github.com/akkadotnet/akka.net/blob/a478c5e8c8d5de97dcf7bcea7e2a80fbaa5e6cc8/src/core/Akka/Actor/Stash/IActorStash.cs#L68

yeah, seems like it, since BeforeIncarnated is a

Plugin behavior applied to underlying <paramref name="actor"/> instance before the actor is being recycled.

Paweł Bańka

@pmbanka

While I'm at it, another question - why is UntypedActor API "recommended for C# 7 users"? Because of better switch support?

Aaron Stannard

@Aaronontheweb

@shersh yep, we use it in our products

@pmbanka I still use ReceiveActor mostly myself

but yeah, C# 7 makes working with the UntypedActor much more bearable

but ReceiveActor can do things switch cannot, such as matching on generics

Paweł Bańka

@pmbanka

thanks @Aaronontheweb. The docs left me quite confused about the difference and whether one of them should be preferred (and why)

Bart de Boer

@boekabart

So is the bottom line that ReceiveActor is likely to be 'heavier' than necessary for C# 7 code?

Aaron Stannard

@Aaronontheweb

@pmbanka which page of the docs?

Paweł Bańka

@pmbanka

@Aaronontheweb the workflow was like that: 1) click http://getakka.net/articles/actors/receive-actor-api.html, start reading. It starts with actors, blah blah, then defining, props, all that jazz. Ok, but I see there is also another API. So I go to 2) http://getakka.net/articles/actors/untyped-actor-api.html, see the beginning is the same, scroll down, creating actors, props, etc. 3) realize that these APIs seem very similar, start hunting down what is the difference, notice OnReceive in one and pattern match in the other one 4) notice the info on top of UntypedActor API page about C# 7, confirming it is mostly about the switch (?)

I think it would be nice to put some section somewhere explainig why are there 2 different APIs, what is the difference and pros/cons

especially since googling akka.net receive actor vs untyped actor does not return anything about the why

Aaron Stannard

@Aaronontheweb

@pmbanka well then

I've been overdue for some technical blog posts on Petabridge's site

sounds like a good one lol

on the official website we mostly just try to give you an explanation for how things work

and what the different tools are meant to be used for

we don't editorialize them much

Stephen Newman

@goodisontoffee

Is there anyone out there that can help me get my head around the implications that leveraging persistence in an existing actor. I've changed the base class and am moving some "commands" over to the construct events, persist, process event pattern but am getting what "feels" like asynchronous processing of the event processing. Is it true to say that:

1) A message is received
2) Message is treated as a command and an event is created from the command
3) Persist is called supplying the event to persist and a handler to be invoked after successful persistence
4) Next message is pulled from the mailbox and processed
5) Persistence completes
6) Handler supplied in 3 is invoked with persisted event

That's how it feels, so I wonder if that is accurate, and is the fix to complete the moving over from messages to Commands/Events and it'll be okay.

Dave

@davenewza

Question around async methods which return data (to an Ask) and PipeTo: would using ContinueWith on faulted tasks be a reasonable way to 'catch' and handle exceptions thrown. Example:

            Receive<SomeRequest>(request =>
            {
                GetSomethingAsync(request)
                    .ContinueWith(t => new FailedResponse(t.Exception), TaskContinuationOptions.OnlyOnFaulted)
                    .PipeTo(Sender);
            });

Where communities thrive

People

Repo info

Activity