MessagePack.MessagePackSerializationException: Unexpected msgpack code 166 (fixstr) encountered. about messagepack-csharp

[AArnott]

I'm not sure why you're seeing what looks like two distinct error messages. The first message means the stream was corrupted (e.g. truncated or content was changed) or you're using a formatter that doesn't reliably generated valid messagpack or read valid messagepack.
The full exception ToString() (with type, message, stacktrace, inner exceptions...) can be very informative when debugging serialization issues. But the error might have occurred earlier in execution and the exception is thrown later when some deserialize suffers from the error made earlier, so the stack trace may be a red herring, but it's always the place to start.

The investigation is almost certainly going to lead to a flaw in code outside this MessagePack library. If you want expert support to help investigate, you may hire me to help.

[dellams]

I am using the standard formatter, as I said in my message NO CODE WAS CHANGED and it stopped working for no reason! So it cannot be my code because it WAS working fine for months so why should it just break for no reason?! It makes no sense.

The only thing I can think of is maybe its something that happened to .net or windows itself? I have never had this before, so I have no idea how to fix this? Any ideas would be really appreciated thanks! :)

[dellams]

MessagePack.MessagePackSerializationException: Failed to deserialize NextGenSoftware.Holochain.HoloNET.Client.HoloNETResponse value.
---> System.IO.EndOfStreamException: Attempted to read past the end of the stream.
at MessagePack.MessagePackReader.ThrowNotEnoughBytesException()
at MessagePack.MessagePackReader.ThrowInsufficientBufferUnless(Boolean condition)
at MessagePack.MessagePackReader.ReadBytes()
at MessagePack.Formatters.NextGenSoftware_Holochain_HoloNET_Client_HoloNETResponseFormatter3.Deserialize(MessagePackReader& reader, MessagePackSerializerOptions options)
at MessagePack.MessagePackSerializer.Deserialize[T](MessagePackReader& reader, MessagePackSerializerOptions options)
--- End of inner exception stack trace ---
at MessagePack.MessagePackSerializer.Deserialize[T](MessagePackReader& reader, MessagePackSerializerOptions options)
at MessagePack.MessagePackSerializer.Deserialize[T](ReadOnlyMemory1 buffer, MessagePackSerializerOptions options, CancellationToken cancellationToken) at NextGenSoftware.Holochain.HoloNET.Client.HoloNETClientBase.DecodeDataReceived(Byte[] rawBinaryData, DataReceivedEventArgs dataReceivedEventArgs). Error Details: MessagePack.MessagePackSerializationException: Failed to deserialize NextGenSoftware.Holochain.HoloNET.Client.HoloNETResponse value. ---> System.IO.EndOfStreamException: Attempted to read past the end of the stream. at MessagePack.MessagePackReader.ThrowNotEnoughBytesException() at MessagePack.MessagePackReader.ThrowInsufficientBufferUnless(Boolean condition) at MessagePack.MessagePackReader.ReadBytes() at MessagePack.Formatters.NextGenSoftware_Holochain_HoloNET_Client_HoloNETResponseFormatter3.Deserialize(MessagePackReader& reader, MessagePackSerializerOptions options) at MessagePack.MessagePackSerializer.Deserialize[T](MessagePackReader& reader, MessagePackSerializerOptions options) --- End of inner exception stack trace --- at MessagePack.MessagePackSerializer.Deserialize[T](MessagePackReader& reader, MessagePackSerializerOptions options) at MessagePack.MessagePackSerializer.Deserialize[T](ReadOnlyMemory1 buffer, MessagePackSerializerOptions options, CancellationToken cancellationToken)
at NextGenSoftware.Holochain.HoloNET.Client.HoloNETClientBase.DecodeDataReceived(Byte[] rawBinaryData, DataReceivedEventArgs dataReceivedEventArgs)

[dellams]

I am using my own web socket lib I built but as I said NO CODE CHANGES were made so not sure why this would all of a sudden break for no reason?

[AArnott]

Thanks for the additional exception details. With that, and your assertion that there are no code changes, my best guess is data corruption. 'No code changes' doesn't direct suspicion toward this library any more than any other code in the application. It does support that some other application code or environmental element is causing data corruption. It's quite easy to write web socket code, or read from a file, or perhaps other places where you're getting your data, to be written poorly such that it only works by chance (even a common chance) yet is prone to fail when those factors change.

This library is quite stable, and has a great many intensive users. This is a free and open source library offered without any kind of warranty (per the popular FOSS license).

As I said, I am available for hire if you choose to take that route.