Sorry, meant to say: on a dedicated process
I know I've sen that at some point, trying to remember the how/why
yes
exactly
and what i did find is that the message is being forwarded to another actor
unlike the others
I'd suggest MAYBE trying Json.NET, if only because once in a while I've had some issues with the current version of wire still has some edge cases that come up. I've seen errors like that when we send types over that Wire can't handle, but usually there's more stack trace to go with it. Can't say with much confidence given the amount of data I'm looking at, but it's easy to try right? =)
I'm bored on a sunday, may as well try to help somebody lol
You may want to place a ticket describing some of the issue (a test or even sample is immeasurably helpful) at https://github.com/akkadotnet/Hyperion/issues
Hyperion is the fork of Wire that will be used in further Akka releases, so that's the best place to have the issue tracked.
Hyperion is the fork of Wire that will be used in further Akka releases, so that's the best place to have the issue tracked.
generally speaking however, Make sure anything you serialize is concrete-typed if you can (i.e. don't use Interfaces on messages, don't slam an arbitrary IEnumerable<> into an object field; instead do a ToList() on it first so there's a well known type on both ends)
Someone who knows more than me please confirm: There's an option in HOCON to serialize all messages. IFF I understand that correctly, that can help detect some serialization errors before they go across remoting and that can help troubleshoot, they will get published to the eventstream.
Keep in mind that you're going to have a perf penalty when doing that, so it's best used for trobleshooting scenarios.
Keep in mind that you're going to have a perf penalty when doing that, so it's best used for trobleshooting scenarios.
i'll check
I think that's the one, you can see where it pushes errors to eventstream in the catch of this region: https://github.com/akkadotnet/akka.net/blob/dev/src/core/Akka/Actor/ActorCell.cs#L310
also note that if the serialization 'fails' things will still work local, so the eventstream is still the go to
to11mtm @to11mtm is just glad he learned something from the groking
wauw
like... feels like the nail in the coffin for java
@Horusiath Hey I was poking at some code thinking about akkadotnet/Hyperion#8 and noticed something that may be useful depending on how elegant MVP versus final solution needs to be...
But it looks like you can set readonly values on a struct if it was created by GetUninitializedObject: Sample here http://share.linqpad.net/499axc.linq
But it looks like you can set readonly values on a struct if it was created by GetUninitializedObject: Sample here http://share.linqpad.net/499axc.linq
once I'll find out why it doesn't work, maybe I'll find out how to make it work :)
basically, the code-gen first we were creating instance using Activator. That was returning a null, so the next we generated cast to a deserialized type. However later, for readonly fields, we were setting them with
FieldInfo.SetValue(object, object), but that requires an object as a first param. So we generated code responsible for casting it back to object (but only for readonly fields). So struct created using activator → casted to its type → casted back to object, was causing an error.
what I've changed, was passing a direct reference to an object returned from activator (so we omitted all casts in this case). That worked.
