Failed to deserialize arguments for Trade (and some others push features)

Issue #47 open
Former user created an issue

Hello. Something happened with "Push settings" and it persists already 3 weeks or more, I was thinking someone already submitted it and was just waiting for fix, but seems like not. Some settings are pushing fine, and some (most important, such as trade or vendor - not). I did not change anything in my addons when it stopped working. Please fix it, it is nightmare to configuring everything 10 times.

Here is Error code: Message: ...e\AddOns\EMA-Classic\Core\Communications-Classic.lua:348: EMA: Failed to deserialize command arguments for Trade from Test. Time: Fri Jun 19 16:28:49 2020 Count: 3 Stack: ...e\AddOns\EMA-Classic\Core\Communications-Classic.lua:348: EMA: Failed to deserialize command arguments for Trade from Eul. C: in function error' ...e\AddOns\EMA-Classic\Core\Communications-Classic.lua:348: in function?' ...las\Libs\CallbackHandler-1.0\CallbackHandler-1.0.lua:119: in function <...las\Libs\CallbackHandler-1.0\CallbackHandler-1.0.lua:119>

...las\Libs\CallbackHandler-1.0\CallbackHandler-1.0.lua:29: in function <...las\Libs\CallbackHandler-1.0\CallbackHandler-1.0.lua:25> ...las\Libs\CallbackHandler-1.0\CallbackHandler-1.0.lua:64: in function Fire' ...s\LibThreatClassic2\Libs\AceComm-3.0\AceComm-3.0.lua:218: in functionOnReceiveMultipartLast' ...s\LibThreatClassic2\Libs\AceComm-3.0\AceComm-3.0.lua:256: in function <...s\LibThreatClassic2\Libs\AceComm-3.0\AceComm-3.0.lua:246>

Locals: <none>

Comments (9)

  1. Jennifer Calladine repo owner

    the part of the addon that is doing this is a 3rd party lib. blizzard has changed somthing in classic to more of less breck addons that use heavy on the comms.

    it be very unliky i can find a fix and fix this one. or though i can not get this to happen on the EU side even using someone profile from the US.

    sorry but for now i can not do anything about this. it might be the end of ema-classic

  2. Daniel Sheppard

    Date: 2020-07-02 12:10:52
    ID: 1
    Error occured in: Global
    Count: 1
    Message: ...e\AddOns\EMA-Classic\Core\Communications-Classic.lua line 348:
       EMA: Failed to deserialize command arguments for Mail from Moobod.
    Debug:
       [C]: error()
       ...e\AddOns\EMA-Classic\Core\Communications-Classic.lua:348: ?()
       ...er4\libs\CallbackHandler-1.0\CallbackHandler-1.0.lua:119:
          ...er4\libs\CallbackHandler-1.0\CallbackHandler-1.0.lua:119
       [C]: ?
       ...er4\libs\CallbackHandler-1.0\CallbackHandler-1.0.lua:29:
          ...er4\libs\CallbackHandler-1.0\CallbackHandler-1.0.lua:25
       ...er4\libs\CallbackHandler-1.0\CallbackHandler-1.0.lua:64: Fire()
       ...\AddOns\EMA-Classic\Libs\AceComm-3.0\AceComm-3.0.lua:218: OnReceiveMultipartLast()
       ...\AddOns\EMA-Classic\Libs\AceComm-3.0\AceComm-3.0.lua:256:
          ...\AddOns\EMA-Classic\Libs\AceComm-3.0\AceComm-3.0.lua:246
    Locals:
    None
    

    I think it will help to have a clean trace.

    As I mentioned in my comments, I think this has to do with the amount of data being sent. First, instead of breaking party/raid, you should probably just separate the commands into individual component sends.

    I did some playing, it isn’t related to \004 or \005 but I would recommend using \028 (File Separator) and \029 (Group separator) instead of \004 and \005. I think this, coupled with breaking apart the messages would help greatly.

  3. Daniel Sheppard

    Gonna throw up a PR shortly, I think I got this licked for you. Couple of different things going on here.

  4. Jennifer Calladine repo owner

    unfortunately that does not work it does not send all the data brecking other parts off the addon

  5. Log in to comment