You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I wasn't able to test it with just the WeakAuras addon since no one else in my raid seems to have this issue and I don't want to delay progress. Disabling the TWWDungeons pack or completely removing it prevents the error from occurring.
The error first occured to me on 27th October. We did also pull Ovi'nax on 24th where the error did not occur. The error always contains the same WeakAura ([TD-Trash] Abyssal Blast) that should not even be loaded in that zone according to its settings
Cannot really tell since other people in my raid don't have this problem. I'd love to help debugging this but I'm to unfamiliar with WoW lua stuff to know where to start.
As it may be performance related, here are my specs:
OS: Windows 11 Pro (10.0.22631)
CPU: AMD Ryzen 5 5600X
RAM: 32GB DDR4
GPU: RTX 3060
Game is running on an NVMe SSD
The video is from November 1st and shows the error occurring.
Right at the beginning of the fight I have a Lag followed by the error. I assume the lag is causing the error (wow aborting the script)
After the lag some auras still work and some don't (like my raid pack and the interrupt weakaura). I assume because they could not be properly initialized since wow has aborted WeakAuras during the initialization of the auras
The error caught references a WeakAura from TWWDungeons that has the url = "https://wago.io/twwdungeons/79 property. When I'm about to delete the TWWDungeons pack you can see the version installed is 1.0.93 with the url https://wago.io/twwdungeons/94. Version 1.0.78 (url /twwdungeons/79) is from September 8th. I keep my auras up to date using WeakAuras Companion so there should not be any aura of that version installed. (see in "Stuff I have tried" for a possible explanation)
After I have deleted the pack and reloaded in the next pull the error occurs again referencing the same aura that should not even exist (see in "Stuff I have tried" for a possible explanation)
Once I have also deleted the twwraid pack (it kind of doesn't make sense, cause the aura is not part of that pack but I didn't know how to otherwise help myself) the error no longer occurs and all the remaining auras work as intended
On October 27th, I did not delete the pack but simply set all auras to never load, which helped back then.
I've restored the backup from October 31st and iterated over all auras trying to find the uid of the report using the follwowing script:
/run for _,d in pairs(WeakAurasSaved.displays) do if d.uid == "1noG0PR0PUZ" then print(d.id) print(d.url) end end
It found the correct aura and d.url resulted in https://wago.io/twwdungeons/94 which is the expected version.
I have performed a full-text search across all files in the SavedVariables folder and found the error in BugGrabber. It has the message, and also the locals containing the twwdungeons/79 URL.
I had a look at BugBrabber's source and it only sets the locals upon seeing an error for the first time. Every additional occurrence of an error that produces the same sanitized message will only cause a counter increment and an update of the session id (related). That's probably why the error still contains the old URL. According to BugGrabber the error first occurred on September 12th at 21:43. I looked it up in WCL and at that exact time we were pulling Sikran on heroic. I probably didn't notice the auras not working since it was only heroic ...
The text was updated successfully, but these errors were encountered:
@emptyrivers yes. That was my bad I deleted the pack yesterday to be able to raid. I corrected the attachments. I've attached two backups from the respective days before each progress day.
One thing I find rather strange: In the error message the aura properties shown contain the part url = "https://wago.io/twwdungeons/79". However, I cannot find that URL anywhere in the WeakAuras.lua file. I keep my auras up to date using the wago client. I even checked the vod from yesterday evening where It clearly showed that Version 1.0.93 ( twwdungeons/94) was installed:
Another strange thing is, that even after I have deleted the pack and did a /reload the error occurred again still having references to twwdungeons/79.
I do also have a WeakAurasArchive.lua at ~27MB if that helps. I'll cut the VoD and will also provide that here.
Is there an existing issue for this?
Description
When pulling Ovi'nax on Mythic with TWWDungeons by Causese installed I get this Lua error and my raid pack (Northern Sky Nerub'ar Palace) no longer works (other WAs like my Class Aura still work)
I wasn't able to test it with just the WeakAuras addon since no one else in my raid seems to have this issue and I don't want to delay progress. Disabling the TWWDungeons pack or completely removing it prevents the error from occurring.
The error first occured to me on 27th October. We did also pull Ovi'nax on 24th where the error did not occur. The error always contains the same WeakAura ([TD-Trash] Abyssal Blast) that should not even be loaded in that zone according to its settings
WeakAuras Version
5.17.4
World of Warcraft Flavor
Retail (Default)
World of Warcraft Region
EU
Tested with only WeakAuras
I got this issue with only WeakAuras enabled
Lua Error
Error from October 27th:
Error from November 1st:
Reproduction Steps
Cannot really tell since other people in my raid don't have this problem. I'd love to help debugging this but I'm to unfamiliar with WoW lua stuff to know where to start.
As it may be performance related, here are my specs:
OS: Windows 11 Pro (10.0.22631)
CPU: AMD Ryzen 5 5600X
RAM: 32GB DDR4
GPU: RTX 3060
Game is running on an NVMe SSD
Last Good Version
No response
Video
Please also have a look a the following video: https://youtu.be/hmIaRvVqVVs
The video is from November 1st and shows the error occurring.
The error caught references a WeakAura from TWWDungeons that has the(see in "Stuff I have tried" for a possible explanation)url = "https://wago.io/twwdungeons/79
property. When I'm about to delete the TWWDungeons pack you can see the version installed is1.0.93
with the urlhttps://wago.io/twwdungeons/94
. Version 1.0.78 (url/twwdungeons/79
) is from September 8th. I keep my auras up to date using WeakAuras Companion so there should not be any aura of that version installed.After I have deleted the pack and reloaded in the next pull the error occurs again referencing the same aura that should not even exist(see in "Stuff I have tried" for a possible explanation)On October 27th, I did not delete the pack but simply set all auras to never load, which helped back then.
Export String
WeakAuras_2024_10_26.zip
WeakAuras_2024_10_31.zip
Stuff I have tried
I've restored the backup from October 31st and iterated over all auras trying to find the uid of the report using the follwowing script:
It found the correct aura and
d.url
resulted inhttps://wago.io/twwdungeons/94
which is the expected version.I have performed a full-text search across all files in the SavedVariables folder and found the error in BugGrabber. It has the message, and also the locals containing the
twwdungeons/79
URL.I had a look at BugBrabber's source and it only sets the locals upon seeing an error for the first time. Every additional occurrence of an error that produces the same sanitized message will only cause a counter increment and an update of the session id (related). That's probably why the error still contains the old URL. According to BugGrabber the error first occurred on September 12th at 21:43. I looked it up in WCL and at that exact time we were pulling Sikran on heroic. I probably didn't notice the auras not working since it was only heroic ...
The text was updated successfully, but these errors were encountered: