Exiled-Team / DiscordIntegration

GNU General Public License v3.0
13 stars 36 forks source link

Fix pls or help #20

Closed Cactus-TV closed 3 years ago

Cactus-TV commented 4 years ago

I have an error, when running the exe. In bot console there is a error "Exception.ToString()". And in my server console there are two types of errors(Exiled version 2.1.0): [2020-08-21 22:03:29.123 +03:00] [DEBUG] [DiscordIntegration_Plugin] System.Runtime.Serialization.SerializationException: Binary stream '161' does not contain a valid BinaryHeader. Possible causes are invalid stream or object version change between serialization and deserialization. at System.Runtime.Serialization.Formatters.Binary.BinaryParser.Run () [0x0012f] in <437ba245d8404784b9fbab9b439ac908>:0 at System.Runtime.Serialization.Formatters.Binary.ObjectReader.Deserialize (System.Runtime.Remoting.Messaging.HeaderHandler handler, System.Runtime.Serialization.Formatters.Binary.BinaryParser serParser, System.Boolean fCheck, System.Boolean isCrossAppDomain, System.Runtime.Remoting.Messaging.IMethodCallMessage methodCallMessage) [0x00069] in <437ba245d8404784b9fbab9b439ac908>:0 at System.Runtime.Serialization.Formatters.Binary.BinaryFormatter.Deserialize (System.IO.Stream serializationStream, System.Runtime.Remoting.Messaging.HeaderHandler handler, System.Boolean fCheck, System.Boolean isCrossAppDomain, System.Runtime.Remoting.Messaging.IMethodCallMessage methodCallMessage) [0x000a2] in <437ba245d8404784b9fbab9b439ac908>:0 at System.Runtime.Serialization.Formatters.Binary.BinaryFormatter.Deserialize (System.IO.Stream serializationStream, System.Runtime.Remoting.Messaging.HeaderHandler handler, System.Boolean fCheck, System.Runtime.Remoting.Messaging.IMethodCallMessage methodCallMessage) [0x00000] in <437ba245d8404784b9fbab9b439ac908>:0 at System.Runtime.Serialization.Formatters.Binary.BinaryFormatter.Deserialize (System.IO.Stream serializationStream, System.Runtime.Remoting.Messaging.HeaderHandler handler, System.Boolean fCheck) [0x00000] in <437ba245d8404784b9fbab9b439ac908>:0 at System.Runtime.Serialization.Formatters.Binary.BinaryFormatter.Deserialize (System.IO.Stream serializationStream, System.Runtime.Remoting.Messaging.HeaderHandler handler) [0x00000] in <437ba245d8404784b9fbab9b439ac908>:0 at System.Runtime.Serialization.Formatters.Binary.BinaryFormatter.Deserialize (System.IO.Stream serializationStream) [0x00000] in <437ba245d8404784b9fbab9b439ac908>:0 at DiscordIntegration_Plugin.ProcessSTT.ReceiveData () [0x00032] in <4e8680b8d48a413e85f97e41744a01f4>:0

[2020-08-21 22:04:46.186 +03:00] [ERROR] [DiscordIntegration_Plugin] System.NullReferenceException: Object reference not set to an instance of an object at System.Runtime.Serialization.Formatters.Binary.BinaryParser.ReadObjectNull (System.Runtime.Serialization.Formatters.Binary.BinaryHeaderEnum binaryHeaderEnum) [0x0005f] in <437ba245d8404784b9fbab9b439ac908>:0 at System.Runtime.Serialization.Formatters.Binary.BinaryParser.Run () [0x000fd] in <437ba245d8404784b9fbab9b439ac908>:0 at System.Runtime.Serialization.Formatters.Binary.ObjectReader.Deserialize (System.Runtime.Remoting.Messaging.HeaderHandler handler, System.Runtime.Serialization.Formatters.Binary.__BinaryParser serParser, System.Boolean fCheck, System.Boolean isCrossAppDomain, System.Runtime.Remoting.Messaging.IMethodCallMessage methodCallMessage) [0x00069] in <437ba245d8404784b9fbab9b439ac908>:0 at System.Runtime.Serialization.Formatters.Binary.BinaryFormatter.Deserialize (System.IO.Stream serializationStream, System.Runtime.Remoting.Messaging.HeaderHandler handler, System.Boolean fCheck, System.Boolean isCrossAppDomain, System.Runtime.Remoting.Messaging.IMethodCallMessage methodCallMessage) [0x000a2] in <437ba245d8404784b9fbab9b439ac908>:0 at System.Runtime.Serialization.Formatters.Binary.BinaryFormatter.Deserialize (System.IO.Stream serializationStream, System.Runtime.Remoting.Messaging.HeaderHandler handler, System.Boolean fCheck, System.Runtime.Remoting.Messaging.IMethodCallMessage methodCallMessage) [0x00000] in <437ba245d8404784b9fbab9b439ac908>:0 at System.Runtime.Serialization.Formatters.Binary.BinaryFormatter.Deserialize (System.IO.Stream serializationStream, System.Runtime.Remoting.Messaging.HeaderHandler handler, System.Boolean fCheck) [0x00000] in <437ba245d8404784b9fbab9b439ac908>:0 at System.Runtime.Serialization.Formatters.Binary.BinaryFormatter.Deserialize (System.IO.Stream serializationStream, System.Runtime.Remoting.Messaging.HeaderHandler handler) [0x00000] in <437ba245d8404784b9fbab9b439ac908>:0 at System.Runtime.Serialization.Formatters.Binary.BinaryFormatter.Deserialize (System.IO.Stream serializationStream) [0x00000] in <437ba245d8404784b9fbab9b439ac908>:0 at DiscordIntegration_Plugin.ProcessSTT.ReceiveData () [0x00032] in <4e8680b8d48a413e85f97e41744a01f4>:0 I wish you help me.

joker-119 commented 4 years ago

I need to know what OS you're running the bot on, etc.

As for the plugin, those errors are likely related to the bot starting to listen on the correct port and accepting the connection, but sending bad info back to the plugin because the bot's crashing.

Cactus-TV commented 4 years ago

Elder version of the bot works properly. The newest doesnt work. I am using windows 10.

joker-119 commented 4 years ago

Which version of the bot are you using? Because the bot hasn't seen any changes since early May.

RiotLeague commented 4 years ago

I'm also having the same problem also on windows 10.

Cactus-TV commented 4 years ago

I am using working DiscordIntegration version 2.1.1

joker-119 commented 4 years ago

I will try rebuilding the bot from scratch as a new project, maybe something got borked that makes it cause issues for Windows users, but I can't at all replicate the issue on Linux, and I have no way to test it on windows so :shrug:

Expect something in maybe a few days, depending how I feel, got a lot of stress and crap from other things I need to deal with first.

For now the workaround is just use a previous build of the bot from one of the releases that works, any of them after May 2020 will be fine, as the bot hasn't been changed since then.