serialization error: Destination array is not long enough about petabridge.cmd-issues HOT 14 CLOSED

Have this fixed! Going to be releasing a v0.3.2 tonight.

from petabridge.cmd-issues.

Petabridge.Cmd v0.3.2 is now live on Chocolatey and NuGet.org. Official announcement will be out tomorrow am. Sorry for the delay on this - wrote a pretty heavy-duty set of model-based tests aimed at nailing this one.

from petabridge.cmd-issues.

Roughly how large is the destination actor hierarchy?

from petabridge.cmd-issues.

Great question, that's what I'm trying to find out. @object any insight?

from petabridge.cmd-issues.

I believe our total hierarchy consists of a few hundred actors, not thousands. So it's relatively decent number.

from petabridge.cmd-issues.

Ok, so this is probably a fairly common use case. Got it. I'll dig into this in more detailed. Do you have a copy of the full error message? Wonder if it's an issue with the way we're using Protobuf.

from petabridge.cmd-issues.

The message I included in the first post is everything I got. I don't see any stack traces related to that in our logs, which is weird :/

from petabridge.cmd-issues.

Hi, any news on this issue?

from petabridge.cmd-issues.

I get this same message doing "cluster show". It lists 4 nodes and then error...

from petabridge.cmd-issues.

Hi folks,

We're on this - have an issue open and am working on reproducing it.

from petabridge.cmd-issues.

FWIW, I also noticed this issue happening when running cluster show command. Our cluster has only 6 nodes.

from petabridge.cmd-issues.

Found the issue; it's this, inside Akka.IO: akkadotnet/akka.net#3183

from petabridge.cmd-issues.

Going to patch that issue as part of the 1.3.3 release.

from petabridge.cmd-issues.

Turns it out wasn't an Akka.IO issue; bug with our serializer not handling some rare but not impossible edge cases involving really, really short frames received from the socket.

from petabridge.cmd-issues.