LUA error in 2024.17

Question

LUA error in 2024.17

hollo6 opened this issue 3 months ago · 11 comments

Getting the following error quite frequently in this version, was happening 2 or 3 versions before as well and now it's back again.

138x SilverDragon_History/module.lua:259: bad argument #1 to 'SetHeight' (Usage: self:SetHeight(height))
[string "=[C]"]: in function SetHeight' [string "@SilverDragon_History/module.lua"]:259: in function RefreshForContents'
[string "@SilverDragon_History/module.lua"]:386: in function <SilverDragon_History/module.lua:385>
[string "=[C]"]: ?
[string "@Blizzard_SharedXMLBase/CallbackRegistry.lua"]:144: in function <...eBlizzard_SharedXMLBase/CallbackRegistry.lua:143>
[string "=[C]"]: ?
[string "@Blizzard_SharedXMLBase/CallbackRegistry.lua"]:147: in function TriggerEvent' [string "@Blizzard_SharedXML/DataProvider.lua"]:81: in function Insert'
[string "@SilverDragon_History/module.lua"]:147: in function AddData' [string "@SilverDragon_History/module.lua"]:103: in function <SilverDragon_History/module.lua:101> [string "=[C]"]: ? [string "@TomTom/libs/CallbackHandler-1.0-8/CallbackHandler-1.0.lua"]:19: in function <...Tom/libs/CallbackHandler-1.0/CallbackHandler-1.0.lua:15> [string "@TomTom/libs/CallbackHandler-1.0-8/CallbackHandler-1.0.lua"]:54: in function Fire'
[string "@SilverDragon/scan/vignettes.lua"]:228: in function WorkOutMobFromVignette' [string "@SilverDragon/scan/vignettes.lua"]:279: in function ?'
[string "@TomTom/libs/CallbackHandler-1.0-8/CallbackHandler-1.0.lua"]:109: in function <...Tom/libs/CallbackHandler-1.0/CallbackHandler-1.0.lua:109>
[string "=[C]"]: ?
[string "@TomTom/libs/CallbackHandler-1.0-8/CallbackHandler-1.0.lua"]:19: in function <...Tom/libs/CallbackHandler-1.0/CallbackHandler-1.0.lua:15>
[string "@TomTom/libs/CallbackHandler-1.0-8/CallbackHandler-1.0.lua"]:54: in function `Fire'
[string "@TomTom/libs/AceEvent-3.0-4/AceEvent-3.0.lua"]:120: in function <...aceTomTom/libs/AceEvent-3.0/AceEvent-3.0.lua:119>

Locals:
(*temporary) = SilverDragonHistoryFrame {
BottomLeftCorner = Texture {
}
RightEdge = Texture {
}
container = Frame {
}
backdropInfo =

{
}
TopRightCorner = Texture {
}
dataProvider =

{
}
resize = Button {
}
clearButton = Button {
}
TopEdge = Texture {
}
TopLeftCorner = Texture {
}
title = FontString {
}
Center = Texture {
}
BottomEdge = Texture {
}
collapseButton = Button {
}
LeftEdge = Texture {
}
BottomRightCorner = Texture {
}
}
(*temporary) = nil

kemayo · Answer 1 · 2024-08-28T00:16:35.000Z

Interesting, I'm not entirely sure how you might have wound up with a non-number saved-height for the window. I can put in something that'll probably help, though.

kemayo · Answer 2 · 2024-08-28T00:26:12.000Z

Could you update to the alpha that'll be generated from that and let me know whether it helped?

hollo6 · Answer 3 · 2024-08-28T05:33:05.000Z

Of course, thanks! I will report back in a few days with the result.

hollo6 · Answer 4 · 2024-08-28T21:15:18.000Z

I'm still getting the same error :(
Also, with the latest version (v2024.17-4-g37766f6), all the rares are getting repeatedly announced even after killed.

kemayo · Answer 5 · 2024-08-28T21:21:56.000Z

As in multiple times in the same encounter, or just announcing again the next time you see it?

hollo6 · Answer 6 · 2024-08-28T21:24:18.000Z

The latter. I see a rare, get a popup, kill it. A few minutes later it is there again and so is the popup. I had it fire for the same rare 3-4 times even.

kemayo · Answer 7 · 2024-08-29T19:12:10.000Z

Would you mind sending me a copy of your savedvariables for SilverDragon at kemayo AT gmail DOT com? I can think of possible reasons, but it'd be easier if I just take a look at how things have wound up getting saved rather than try to describe it all. 😂

rursache · Answer 8 · 2024-08-31T12:52:41.000Z

@kemayo the history module is bugged, i have it disabled and it still shows up:

walkaround is to disable the module:

kemayo · Answer 9 · 2024-08-31T14:57:44.000Z

Okay! I believe that was was going on for @hollo6 was related to profile-switching, and the new alpha should fix that.

@rursache Are you also using profile switching? It failing to properly cope if the default profile loaded with the module enabled then switching to another profile that had it disabled was a thing that was happening, but if you're not using profiles then it'd presumably be something else...

rursache · Answer 10 · 2024-08-31T15:07:14.000Z

@kemayo i am not, im using the default/global profile

hollo6 · Answer 11 · 2024-09-01T10:23:43.000Z

I think I figured out why the rares were showing up multiple times after already killed.
This was happening around the Spreading the Light event area where several rares have a chat/emote when they spawn, so I think it's the evergreen issue of chat spawn detection not respecting ignore and already killed rules (same as #234 ).

Share to