Daily Addon Error Reports

[the_real_seebs]

Would be nice if bug report also included number of reported errors, not just percentage.

I think the reason that's not there is that people could possibly use it to derive usage statistics.

[Kreiri]

I think the reason that's not there is that people could possibly use it to derive usage statistics.

Usage of what, Rift or addon?
I can derive addon usage statistics simply looking at addon stats on at Riftui. And deriving Rift usage statistics from number of reported errors is like deriving Rift usage statistics from number of people in your guild.

[the_real_seebs]

Usage of what, Rift or addon?
I can derive addon usage statistics simply looking at addon stats on at Riftui. And deriving Rift usage statistics from number of reported errors is like deriving Rift usage statistics from number of people in your guild.

Maybe, maybe-not. I could see people thinking of a way to extract statistics that could at least show relative activity levels in some way. Not sure what it would be.

[DoomSprout]

One of the checks is that errors which occured for only one user won't be sent. As long as you're not doing development on two clients, you'll never see your dev errors.

Cool, nice thinking there!

[Lorandii]

Just curious, what is the time frame for the daily reports to stop after an addon is fixed? I fixed both LibStub and LibCallbackHandler, tested on the PTS until no errors occured, and updated the versions. However, the error report got sent again for the previous, broken, copies.

[Imhothar]

Just curious, what is the time frame for the daily reports to stop after an addon is fixed? I fixed both LibStub and LibCallbackHandler, tested on the PTS until no errors occured, and updated the versions. However, the error report got sent again for the previous, broken, copies.

I think the report contains the last 7 days.
But updating the addon doesn't mean everybody uptated their copy. Some people are running weeks, even months old versions of addons. All you can do is push the version number and cross-check it with the version reported in the mail.

[Lorandii]

I think the report contains the last 7 days.
But updating the addon doesn't mean everybody uptated their copy. Some people are running weeks, even months old versions of addons. All you can do is push the version number and cross-check it with the version reported in the mail.

Thanks for the heads-up. While previous versions of my libs were downloaded a few thousand times, that was before the API gained Utility.Event.Create, and my port offered the only solution, buggy though it was. Before yesterday, the last update I provided was almost exactly a year ago. I have to thank Trion for the bug report system, as without it, I would not have known about the bugs I have since crushed.

So, yay!

[Thorarin]

Are the reports sent to the email address in the TOC file of the addon?
I may have to create an email alias that sends this stuff to all the authors instead of just one.

[Noshei]

Are the reports sent to the email address in the TOC file of the addon?
I may have to create an email alias that sends this stuff to all the authors instead of just one.

yes they are. Google is great for this type of thing, it's very easy to setup rules to forward messages.

[Mere]

It'd be useful if the performance warnings could be merged on the bottom function, in the first email I have 4 out of 5 being the same problem, just different lines.

Eg, below are all the same area of code (Note I have now improved this code, so hopefully it'll be less common)

I suspect that it might only be possible to merge them into 2 warnings, as they're actually in two different functions at the bottom of the stack, but that might help let me see more places to fix code

btw, much as I might be complaining, this is an awesome feature to have I just need to improve some areas of code so that hopefully more of the 80% of other errors will get mailed to me

4% of reported errors:
Error: performance warning
In MereHealingFrames / MereHealingFrames.Events.PlayerReady
stack traceback:
MereHealingFrames/HealingPanelLayout.lua:271: in function 'RelayPanels'
MereHealingFrames/HealingPanelLayout.lua:508: in function 'SetVisible'
MereHealingFrames/HealingPanelLayout.lua:592: in function 'GroupLeave'
MereHealingFrames/RaidManagement.lua:323: in function 'CheckForStrays'
MereHealingFrames/Events.lua:139: in function <MereHealingFrames/Events.lua:135>
SafesRaidManager/SafesRaidManager.lua:678: in function <SafesRaidManager/SafesRaidManager.lua:661>


4% of reported errors:
Error: performance warning
In MereHealingFrames / MereHealingFrames.Events.PlayerReady
stack traceback:
MereHealingFrames/HealingPanelLayout.lua:273: in function 'RelayPanels'
MereHealingFrames/HealingPanelLayout.lua:508: in function 'SetVisible'
MereHealingFrames/HealingPanelLayout.lua:592: in function 'GroupLeave'
MereHealingFrames/RaidManagement.lua:323: in function 'CheckForStrays'
MereHealingFrames/Events.lua:139: in function <MereHealingFrames/Events.lua:135>
SafesRaidManager/SafesRaidManager.lua:678: in function <SafesRaidManager/SafesRaidManager.lua:661>

4% of reported errors:
Error: performance warning
In MereHealingFrames / MereHealingFrames.Events.PlayerReady
stack traceback:
MereHealingFrames/HealingPanelLayout.lua:496: in function 'RelayLayoutPanels'
MereHealingFrames/HealingPanelLayout.lua:292: in function 'RelayPanels'
MereHealingFrames/HealingPanelLayout.lua:508: in function 'SetVisible'
MereHealingFrames/HealingPanelLayout.lua:592: in function 'GroupLeave'
MereHealingFrames/RaidManagement.lua:323: in function 'CheckForStrays'
MereHealingFrames/Events.lua:139: in function <MereHealingFrames/Events.lua:135>
SafesRaidManager/SafesRaidManager.lua:678: in function <SafesRaidManager/SafesRaidManager.lua:661>

4% of reported errors:
Error: performance warning
In MereHealingFrames / MereHealingFrames.Events.PlayerReady
stack traceback:
MereHealingFrames/HealingPanelLayout.lua:497: in function 'RelayLayoutPanels'
MereHealingFrames/HealingPanelLayout.lua:292: in function 'RelayPanels'
MereHealingFrames/HealingPanelLayout.lua:508: in function 'SetVisible'
MereHealingFrames/HealingPanelLayout.lua:592: in function 'GroupLeave'
MereHealingFrames/RaidManagement.lua:323: in function 'CheckForStrays'
MereHealingFrames/Events.lua:139: in function <MereHealingFrames/Events.lua:135>
SafesRaidManager/SafesRaidManager.lua:678: in function <SafesRaidManager/SafesRaidManager.lua:661>

[Kreiri]

I think the report contains the last 7 days.
But updating the addon doesn't mean everybody uptated their copy. Some people are running weeks, even months old versions of addons. All you can do is push the version number and cross-check it with the version reported in the mail.

According to my reports some people still run KBB v.0.1. The one I wrote year ago.

[dOxxx]

I started getting these errors a few days ago:

1.8.1

100% of reported errors:
Error: file 'eventproxy.lua' not found
In LibSimpleWidgets

v1.8.1 is quite old, from last year some time. Zorba, I thought you changed it so that it would report the error to the containing addon?

[ZorbaTHut]

I started getting these errors a few days ago:

v1.8.1 is quite old, from last year some time. Zorba, I thought you changed it so that it would report the error to the containing addon?

I did, and I just tested it on live It results in an error like this:

Error: file 'EmbeddedAddon/missing_file.lua' not found
    In ContainingAddon

Chances are good that people are somehow ending up with broken installs.

[dOxxx]

I did, and I just tested it on live It results in an error like this:

Error: file 'EmbeddedAddon/missing_file.lua' not found
    In ContainingAddon

Chances are good that people are somehow ending up with broken installs.

I'm 100% certain none of my releases had missing files. I guess somebody has unzipped it directly into their Addons folder and messed with the contents. I wish they'd fix it.

[dOxxx]

More weirdness:

LibSimpleWidgets

1.8.1

77% of reported errors:
Error: file 'eventproxy.lua' not found
In LibSimpleWidgets
23% of reported errors:
Error: file ''eventproxy.lua'' not found
In LibSimpleWidgets