mudlet-makers team mailing list archive

[Vadim Peretokin <vperetokin@xxxxxxxxx>]

It's clear that JSON decoding is receiving a corrupted string:

[ERROR:] object:<event handler function> function:<mmhrv_resetroom>
         <[string "local currentroom..."]:3: attempt to index field 'Info' (a nil value)>
[ERROR:] object:<JSON decoder error:> function:<json_to_value>
         <Lua error:InvalidJSONInput: lexical error: invalid char in json text.
                   { "location": "inv",.Items.Update { "location": "in
                     (right here) ------^
 at lua-yajl2-linux.c line 310>
[ERROR:] object:<JSON decoder error:> function:<json_to_value>
         <Lua error:InvalidJSONInput: parse error: trailing garbage
                { "locatttrib": "gt" } }
                     (right here) ------^
 at lua-yajl2-linux.c line 310>
[ERROR:] object:<JSON decoder error:> function:<json_to_value>
         <Lua error:InvalidJSONInput: lexical error: invalid char in json text.
          183408", "name": "a stem of4"location": "inv", "item": { "id
                     (right here) ------^
 at lua-yajl2-linux.c line 310>
[ERROR:] object:<JSON decoder error:> function:<json_to_value>
         <Lua error:InvalidJSONInput: lexical error: invalid string in json text.
                     { "locatttrib": 9trib": "gt" } }
                     (right here) ------^
 at lua-yajl2-linux.c line 310>
[ERROR:] object:<JSON decoder error:> function:<json_to_value>
         <Lua error:InvalidJSONInput: parse error: object key and value must be separated by a 
colon (':')
           "a9 of 1090 galingale stems", "attrib": "gt" } }
                     (right here) ------^
 at lua-yajl2-linux.c line 310>
[ERROR:] object:<JSON decoder error:> function:<json_to_value>

-- 
You received this bug notification because you are a member of Mudlet
Makers, which is subscribed to Mudlet.
https://bugs.launchpad.net/bugs/918419

Title:
  gmcp "hangs" when dealing with a lot of items

Status in Mudlet the MUD client:
  Confirmed

Bug description:
  When dealing with a lot of individual items, your connection can look
  like its stuck: you don't receive any information back from the server
  and can't send anything.

  I found the problem on Achaea, and it only works when using gmcp. An easy way to simulate it would be the following:
  OUTR ALL KOLA (or whatever plant you have tons of)
  SPLIT KOLA INTO GROUPS OF 1 (do this till all your kola is split into individual items)
  COMBINE ALL KOLA

  This last step will cause the connection to hang. This is on an empty
  profile with only gmcp enabled.

  To confirm that this is a Mudlet-specific bug and not an Achaean one,
  I tried with another client (tintin++). With gmcp enabled there (and
  the Char, Room and Char.Items modules enabled), the combining worked.

  
  My Mudlet version is one compiled from git from a week or two ago, on Archlinux.

To manage notifications about this bug go to:
https://bugs.launchpad.net/mudlet/+bug/918419/+subscriptions