5 - Infinite Repeating Ding Announcement

Ok... I know this is an error that tracking it down could drive you up the wall... but I have one player in our guild that seems to break ReadySetDing.

Sweetteats ... is a Warrior in our guild and when ever she levels up, readySetDing goes crazy ... (I should say it ONLY occurs on this character and no one else in the guild)

            ["Sweetteats"] = {
                53, -- [1]
                [55] = {
                    1297582538, -- [1]
                    "2011.02.13 02:35:38", -- [2]
RSD will repreat post her level over and over and over again

Name Size MD5
ReadySetDing.lua 35.2 KiB 8082b549b684...
_Swatter.lua 238.2 KiB 135d5141b351...
User When Change
Ketho May 24, 2013 at 12:22 UTC Changed status from Accepted to Fixed
Ketho Jun 09, 2011 at 21:27 UTC Changed status from Fixed to Accepted
Ketho Feb 15, 2011 at 18:26 UTC Changed status from Replied to Fixed
MarkParish Feb 14, 2011 at 06:04 UTC

Added attachment _Swatter.lua

MarkParish Feb 14, 2011 at 06:03 UTC Changed status from Waiting to Replied
Ketho Feb 13, 2011 at 12:55 UTC Changed status from New to Waiting
MarkParish Feb 13, 2011 at 08:18 UTC

Added attachment ReadySetDing.lua

MarkParish Feb 13, 2011 at 08:18 UTC Create

You must login to post a comment. Don't have an account? Register to get one!

  • Avatar of Ketho Ketho Jun 09, 2011 at 21:26 UTC - 0 likes

    Reopening this, from this comment:


    Fri, 4 Mar 2011 18:10:08

    Hey there, nothing new to update you on, everything seems to be fine with RSD. The only "kinda" error that has occured recently with RSD was not your fault or my fault, but Blizzard's fault. The guild I'm in recruited a new player named Slestro, well Blizzard did some weird when he was added to the guild ... we some had at one point 3 Slestro in the Guild Roster. You can guess what happened when he Ding! RSD went crazy because it was seeing the Ding from 3 Slestro. Anyway, with a lot of talking to GMs, we got the problem solved (they admited it was all on their end of things) and after that RSD had no problems.

    I also recently experienced this...
    So I guess it's a blizzard bug, and finding a fix or workaround would be kinda difficult

  • Avatar of Ketho Ketho Feb 15, 2011 at 18:25 UTC - 0 likes

    Sorry for the late update~

    I'm pretty sure I was able to fix it with your error logs on 3 (!) different versions!

    That made me remember somewhere from the back of my head, that GetGuildRosterInfo() in rare cases returns only a nil, so I added a sanity check for that ...

    Without your error logs + SavedVars I would have bashed my head through my keyboard

    ... I even fixed some more bugs I oversaw, while at it. I'm still working on ReadySetDing, but I must say, I'm really, really happy with your feedback. (n_n)

    You can see I really like colors, everywhere T.T

    Last edited Feb 15, 2011 by Ketho
  • Avatar of MarkParish MarkParish Feb 14, 2011 at 06:03 UTC - 0 likes

    Yeah, I've been a computer programmer/analyst for 20+ years now, so while I'm not comfortable with programming in LUA, I have an eye for problems that will be hard to track down.

    (I switched back to a previous version of ReadySetDing [], to see if the problem continued to reproduce itself)

    I'm using Swatter, and I'll upload the !Swatter.lua file as well, but I'm guessing the important pieces you're looking for are:

                ["message"] = "Interface\\AddOns\\ReadySetDing\\ReadySetDing.lua:1479 attempt to compare nil with number",
                ["count"] = 23,
                ["timestamp"] = "2011-02-13 03:06:43",
                ["context"] = "Global",
                ["stack"] = "(tail call): ?\nInterface\\AddOns\\ReadySetDing\\ReadySetDing.lua:1479 in function `?'\n...ibDataBroker\\CallbackHandler\\CallbackHandler-1.0.lua:147 in function <...ibDataBroker\\CallbackHandler\\CallbackHandler-1.0.lua:147\n[string \"safecall Dispatcher[1]\"]:4: in function <[string \"safecall Dispatcher[1]\"]:4>\n[C]: ?\n[string \"safecall Dispatcher[1]\"]:13: in function `?'\n...ibDataBroker\\CallbackHandler\\CallbackHandler-1.0.lua:92 in function `Fire'\n...rface\\AddOns\\Omen\\Libs\\AceEvent-3.0\\AceEvent-3.0.lua:120 in function <...rface\\AddOns\\Omen\\Libs\\AceEvent-3.0\\AceEvent-3.0.lua:119\n",

                ["message"] = "Interface\\AddOns\\ReadySetDing\\Core.lua:1419 table index is nil",
                ["count"] = 2,
                ["timestamp"] = "2011-02-13 03:49:12",
                ["context"] = "Global",
                ["stack"] = "(tail call): ?\nInterface\\AddOns\\ReadySetDing\\Core.lua:1419 in function `?'\n...ibDataBroker\\CallbackHandler\\CallbackHandler-1.0.lua:147 in function <...ibDataBroker\\CallbackHandler\\CallbackHandler-1.0.lua:147\n[string \"safecall Dispatcher[1]\"]:4: in function <[string \"safecall Dispatcher[1]\"]:4>\n[C]: ?\n[string \"safecall Dispatcher[1]\"]:13: in function `?'\n...ibDataBroker\\CallbackHandler\\CallbackHandler-1.0.lua:92 in function `Fire'\n...rface\\AddOns\\Omen\\Libs\\AceEvent-3.0\\AceEvent-3.0.lua:120 in function <...rface\\AddOns\\Omen\\Libs\\AceEvent-3.0\\AceEvent-3.0.lua:119\n",

  • Avatar of Ketho Ketho Feb 13, 2011 at 12:54 UTC - 0 likes

    Thanks for grabbing the SavedVariables :)
    You are idd right that this could drive me up the wall :(

    From what I can see:

    • The current level 53 is saved to index [1]
      - That's bad, since it should be at least level 55 now
    • She dinged to level 54 while you were offline (!) oh crap ><
    • She dinged to level 55 while you were online
    • ReadySetDing normally first calculates the Level Time & Level Speed, and then shows/announces it
    • .. but then it gets an error, and won't save the new level, compares the current level with the unsaved level, and thinks she dinged every 11 seconds.. voila! new world record :D

    But I'm not sure where exactly it's going wrong without an error report ...
    Do you have [Display Lua Errors] enabled?
    Or could you use BugSack / Swatter to get the error log and post it?
    v0.78 Beta

    Last edited Feb 13, 2011 by Ketho


Last updated
May 24, 2013
Feb 13, 2011
Fixed - Developer made requested changes. QA should verify.
Defect - A shortcoming, fault, or imperfection
Medium - Normal priority.

Reported by

Possible assignees