funkydude / bugsack Goto Github PK

Just thought I switched to the fifth dimension today because fetchFromDatabase() fetches stack-traces from all sessions and thus can report non-existing stack-traces involving removed add-ons...

This can make debugging very difficult or even impossible if one doesn't come to suspect a bug in BugGrabber itself...

Changing fetchFromDatabase() to the following in BugGrabber.lua fixes the problem:

local function fetchFromDatabase(database, target)

        local currentSessionId =  addon:GetSessionId()

	for i, err in next, database do
		if err.message == target and err.session == currentSessionId then
			-- This error already exists
			err.counter = err.counter + 1

			return table.remove(database, i)
		end
	end
end

Describe the problem

Bugsack generating error each time I log in

What steps will reproduce the problem?

1. log in

Consider attaching a screenshot below to help describe your issue (Attach directly, do not link to other websites)

What version of the addon are you using? (Stating 'latest' is not useful)

9.1.1-classic

Do you have an error log of what happened?

BugSack-v9.1.1\core.lua:130: attempt to call method 'GetSessionId' (a nil value)

Any additional information? (example: WoW language if not English)

I'm not sure if this is intended behavior, but unchecking the 'minimap icon' option just fades out the button instead of disabling it.

So whenever I mouse over the minimap, the bugsack icon appears and hangs around for a bit.

Would there be a way to actually disable it? I already have it on the databroker, so I would like my minimap to be completely clear.

Hello

I would like to ask if there is an Option to disable the "Addon_Action_Blocked" Error Message beeing send to Bugsack.

Thanks

Alt click and shift click still clear bugs and reload UI, but normal clicking gives an error (which I can't copy the entire thing, because bugsack can't open :P), but here's line 1:
BugSack\sack.lua:317: attempt to call method 'SetBackdrop' (a nil value)

1:

8x BugSack\Libs\LibDBIcon-1.0\LibDBIcon-1.0-34.lua:72: Attempt to access forbidden object from code tainted by an AddOn
[C]: in function `Hide'
BugSack\Libs\LibDBIcon-1.0\LibDBIcon-1.0-34.lua:72: in function <BugSack\Libs\LibDBIcon-1.0\LibDBIcon-1.0.lua:70>
[C]: ?

2:

10x BugSack\Libs\LibDBIcon-1.0\LibDBIcon-1.0-34.lua:61: Attempt to access forbidden object from code tainted by an AddOn
[C]: in function `SetOwner'
BugSack\Libs\LibDBIcon-1.0\LibDBIcon-1.0-34.lua:61: in function <BugSack\Libs\LibDBIcon-1.0\LibDBIcon-1.0.lua:57>
[C]: ?

3:

301x SharedXML\SharedUIPanelTemplates.lua:672: Attempt to access forbidden object from code tainted by an AddOn
[C]: in function IsOwned' SharedXML\SharedUIPanelTemplates.lua:672: in function PanelTemplates_SelectTab'
BugSack\sack.lua:118: in function <BugSack\sack.lua:32>
BugSack\sack.lua:445: in function <BugSack\sack.lua:440>
BugSack\sack.lua:464: in function OpenSack' BugSack\core.lua:59: in function <BugSack\core.lua:46> [string "safecall Dispatcher[2]"]:4: in function <[string "safecall Dispatcher[2]"]:4> [C]: ? [string "safecall Dispatcher[2]"]:13: in function ?'
...ist\libs\CallbackHandler-1.0\CallbackHandler-1.0-6.lua:90: in function Fire' !BugGrabber\BugGrabber.lua:149: in function <!BugGrabber\BugGrabber.lua:147> !BugGrabber\BugGrabber.lua:370: in function <!BugGrabber\BugGrabber.lua:292> ... [C]: ? [string "safecall Dispatcher[3]"]:13: in function ?'
...ist\libs\CallbackHandler-1.0\CallbackHandler-1.0-6.lua:90: in function Fire' ...s\AckisRecipeList\libs\AceEvent-3.0\AceEvent-3.0-4.lua:120: in function <...s\AckisRecipeList\libs\AceEvent-3.0\AceEvent-3.0.lua:119> [C]: in function UseAction'
FrameXML\SecureTemplates.lua:346: in function handler' FrameXML\SecureTemplates.lua:619: in function SecureActionButton_OnClick'
FrameXML\ActionButton.lua:100: in function <FrameXML\ActionButton.lua:94>
FrameXML\ActionButton.lua:136: in function `ActionButtonDown'
[string "ACTIONBUTTON2"]:2: in function <[string "ACTIONBUTTON2"]:1>

Locals:
nil

1x [ADDON_ACTION_BLOCKED] AddOn 'Ace3' tried to call the protected function 'SetTargetClampingInsets()'.
!BugGrabber\BugGrabber.lua:519: in function <!BugGrabber\BugGrabber.lua:519>
[C]: in function SetTargetClampingInsets' ...eBlizzard_NamePlates\Blizzard_NamePlates.lua:274: in function SetupClassNameplateBars'
...eBlizzard_NamePlates\Blizzard_NamePlates.lua:96: in function `OnNamePlateAdded'
...eBlizzard_NamePlates\Blizzard_NamePlates.lua:51: in function <...eBlizzard_NamePlates\Blizzard_NamePlates.lua:42>

Locals:
InCombatSkipped

5x ...eBlizzard_NamePlates\Blizzard_NamePlates.lua:185: Usage: GetRaidTargetIndex(unit)
[C]: in function GetRaidTargetIndex' ...eBlizzard_NamePlates\Blizzard_NamePlates.lua:185: in function OnRaidTargetUpdate'
...eBlizzard_NamePlates\Blizzard_NamePlates.lua:99: in function `OnNamePlateAdded'
...eBlizzard_NamePlates\Blizzard_NamePlates.lua:51: in function <...eBlizzard_NamePlates\Blizzard_NamePlates.lua:42>

Locals:
(*temporary) = nil

1x ...eBlizzard_NamePlates\Blizzard_NamePlates.lua:443: Action[FrameMeasurement] failed because[Can't measure restricted regions]: attempted from: :GetLeft().
[C]: in function GetLeft' ...eBlizzard_NamePlates\Blizzard_NamePlates.lua:443: in function GetPreferredInsets'
...eBlizzard_NamePlates\Blizzard_NamePlates.lua:138: in function UpdateInsetsForType' ...eBlizzard_NamePlates\Blizzard_NamePlates.lua:122: in function ApplyFrameOptions'
...eBlizzard_NamePlates\Blizzard_NamePlates.lua:93: in function `OnNamePlateAdded'
...eBlizzard_NamePlates\Blizzard_NamePlates.lua:51: in function <...eBlizzard_NamePlates\Blizzard_NamePlates.lua:42>

Locals:
(*temporary) = {
otherHealPrediction = {
}
b = 1
myHealAbsorbLeftShadow = {
}
border = {
}
background = {
}
overAbsorbGlow = {
}
barTexture = {
}
0 =
r = 0.667000
totalAbsorb = {
}
myHealPrediction = {
}
g = 0.667000
totalAbsorbOverlay = {
}
myHealAbsorbRightShadow = {
}
overHealAbsorbGlow = {
}
myHealAbsorb = {
}

Hello, just a friendly note. On Wago, the addon developers are also paid, as I have read. Maybe that's a great option to offer your addon somewhere else. We can download their addon with apps like WoWup and they get paid for their work too! :)
Curse locks WoWup.

This is BugGrabber related but that add-on doesn't have its own issues function so reporting it here.

Seems there are scenarios where that code line isn't working correctly, considering I've apparently had this happen 603 times I wouldn't mind some sort of protection be added so it doesn't show up for me when it happens.

603x (null)
!BugGrabber\BugGrabber.lua:578: in function <!BugGrabber\BugGrabber.lua:578>

Describe the problem

Interface\AddOns\BugSack\sack.lua:318: attempt to call method 'SetBackdrop' (a nil value) appears when attempting to open bugsack in retail wow.

What steps will reproduce the problem?

1. Install BugSack [v9.2.1] (2022-02-28)
2. Launch World of Warcraft Retail (9.2)
3. Log in on any character
4. Attempt to open BugSack to view possible bugs/issues
5. Observe error and bugsack not opening

What version of the addon are you using? (Stating 'latest' is not useful)

BugSack [v9.2.1] (2022-02-28) - r252

Do you have an error log of what happened?

Interface\AddOns\BugSack\sack.lua:318: attempt to call method 'SetBackdrop' (a nil value)

I was thinking that with monitors and resolutions as they are today, have a much larger "sack window" would be nice for being able to make it so that each line of the stack trace could be individual calls (i.e., make the stack trace easier to read.) Right now I find myself having to copy/paste the sack text into another editor just so my eyes can better parse it.

Would there be an interest in a pull request to add this functionality? I was thinking of just adding two configuration options: one for width and one for height with a box to type in the static integer. The default would stay as it is right now.

Or, if the addon author would prefer to do it, that's fine with me too. I just think the sack could be a lot more useful if it were bigger on the screen, and think that we're now to the point at which monitors and resolutions can handle a sack that's both wider and taller.

Thanks.

something that really grinds my gear is that it keeps spamming me with messages in the chat that im getting errors from addons like its really going at it i can't even see messages in the chat cause it spamming so much. the addons that are giving me error is working for what i need them to and the game performance is not impacted. it would be great if you could mute all notifications or make it only send out 1 message per session (not including UI reload).
i don't know if there is a option like this already i have only found the mute audio option...
please add a darn mute all messages option!

I got an error when I was trying to send a report for the first time.
No error occur after the first time.

Version: v7.3.2

1x BugSack\sack.lua:375: attempt to index upvalue 'currentSackContents' (a nil value)
BugSack\sack.lua:375: in function <BugSack\sack.lua:374>

Locals:
(*temporary) = nil
(*temporary) = 1
(*temporary) = nil
(*temporary) = nil
(*temporary) = "attempt to index upvalue 'currentSackContents' (a nil value)"
currentSackContents = nil
currentErrorIndex = 1
window = BugSackFrame {
 0 = <userdata>
}

I been using your github to download and update BugSack, but I can't find Bug Grabber. Any chance you would host it here

A new issue in BfA (not with your addon, but with WoW itself reporting a previously hidden error) is that some XML-based libraries are very common, found in multiple addons, and will proc errors on every reload reporting that the objects already exist.

It would be really nice if we could have a checkbox option to filter out these harmless errors that there's really no point in seeing anyway. Are you open to blocking those?

Will you add support for BugSack and Buggrabber for WoW Classic 1.13.2 ?

When you mouse over the title of the BugSack window, you get the "Quick tips" tooltip that says you can left click to drag the window or right click to open the interface options. While this tooltip is up, left click and right click do not in fact do anything. There is a tiny margin around the scrollable text window which you can drag from, but right clicking that doesn't do anything.

Double click to filter does work.

Would it be possible to implement a function to create a txt file in some order with this errors?

The ability to alt-click the BugSack icon to clear recorded bugs is important for development..
It always been possible to quickly check the stack at a glance while testing changes, alt-click to clear, replicate one issue in interface, single line pops up in tooltip, shift-click to reload, without having to open the options or the main window.

Please consider [making it an option] for who actually used it, at least.. Or [move the wipe button to the main interface instead of settings].
Thanks

When an error occurs frequently (every frame) and the callstack context is long, opening BugSack can cause huge frame drops.

As a proof of concept if you import this WeakAura it will trigger an error every frame in a long function. Opening BugSack while the errors are still being generated freezes my game to <5 FPS. I know this is an artificial example but I have encountered this issue in the wild several times.

I have traced the issue to colorStack, which was taking 200ms/call with this example. Specifically this line:

ret = ret:gsub("([^\\]+%.lua)", "|cffffffff%1|r") -- Lua files

causes a lot of backtracking. Replacing it with

ret = ret:gsub("\\([^\\]+%.lua)", "\\|cffffffff%1|r") -- Lua files

fixes the problem.

319x Couldn't find frame parent: WorldMapDetailFrame

Not sure if it is just something with another addon?
And it does not really affect any gameplay.

EDIT: But it does say the Error is in Bugsack....

/Calth

Describe the problem

formerly alt-click would clear the bug sack icon, as of last update it opens the bug report. shift click reloads ui, as before. control-click shows the report window, alt-click is duplicating control-click

What steps will reproduce the problem?

1. alt-click icon - see report popup

Consider attaching a screenshot below to help describe your issue (Attach directly, do not link to other websites)

What version of the addon are you using? (Stating 'latest' is not useful)

Interface: 20501

Version: v9.0.3

Do you have an error log of what happened?

there is no error, just a change of function - perhaps by mistake

Any additional information? (example: WoW language if not English)

Please consider making BugGrabber available on GitHub, so that it and BugSack can be installed without relying on Curse.

It seems, BugSack is having issues with the changes regarding SetBackdrop (sack.lua: 317).

Also see: https://www.wowinterface.com/forums/showthread.php?p=336629#post336629

Describe the problem

Setpoint error.

What steps will reproduce the problem?

1. Logging in

Consider attaching a screenshot below to help describe your issue (Attach directly, do not link to other websites)

What version of the addon are you using? (Stating 'latest' is not useful)

Version 2.52

Do you have an error log of what happened?

1x Interface_TBC\FrameXML\UIParent.lua:2535: Action[SetPoint] failed because[SetPoint would result in anchor family connection]: attempted from: QuestWatchFrame:SetPoint.
[string "=[C]"]: in function SetPoint' [string "@Interface_TBC\FrameXML\UIParent.lua"]:2535: in function UIParentManageFramePositions'
[string "@Interface_TBC\FrameXML\UIParent.lua"]:1827: in function <Interface_TBC\FrameXML\UIParent.lua:1814>
[string "=[C]"]: in function SetAttribute' [string "@Interface_TBC\FrameXML\UIParent.lua"]:2546: in function UIParent_ManageFramePositions'
[string "@Blizzard_UIWidgets\Blizzard_UIWidgetBelowMinimapFrame.lua"]:25: in function layoutFunc' [string "@Blizzard_UIWidgets\Blizzard_UIWidgetManager.lua"]:225: in function UpdateWidgetSetContainerLayout'
[string "@Blizzard_UIWidgets\Blizzard_UIWidgetManager.lua"]:318: in function ProcessWidgetSet' [string "@Blizzard_UIWidgets\Blizzard_UIWidgetManager.lua"]:340: in function UpdateAllWidgets'
[string "@Blizzard_UIWidgets\Blizzard_UIWidgetManager.lua"]:33: in function <...dOns\Blizzard_UIWidgets\Blizzard_UIWidgetManager.lua:31>

Locals:
(*temporary) = QuestWatchFrame {
0 =
FadeOut = {
}
FadeIn = {
}
}
(*temporary) = "TOPRIGHT"
(*temporary) = "MinimapCluster"
(*temporary) = "BOTTOMRIGHT"
(*temporary) = 0
(*temporary) = 0

Any additional information? (example: WoW language if not English)

I have gotten this weird error the past day or so, not quite sure what to make out of it, and well, I can not report it directly on the BugGrabber addon.

129x Deferred XML Node object named L_UIDropDownListTemplate already exists
!BugGrabber\BugGrabber.lua:578: in function <!BugGrabber\BugGrabber.lua:578>

Locals:
nil

129x Deferred XML Node object named L_UIDropDownMenuTemplate already exists
!BugGrabber\BugGrabber.lua:578: in function <!BugGrabber\BugGrabber.lua:578>

Locals:
nil

172x Deferred XML Node object named L_UIDropDownMenuButtonTemplate already exists
!BugGrabber\BugGrabber.lua:578: in function <!BugGrabber\BugGrabber.lua:578>

Locals:
nil

Overwolf has blocked wowup from using the curseforge API, please consider a alternative hosting for BugGrabber so wowup users can get updates. Wowup supports github, wowuphub, wago and wowinterface.

have a question to if you should send the error messages

Can we please have a slash command to clear errors for using this command in a macro?
Something like "/swatter clear", but for BugSack.

I'm going to look into embedding BugGrabber into my addon to improve some of the data reported, but it occurs to me that if it's possible it would help a lot of authors if BugSack's report included the Addon Version so we can tell if people are running out of date addons.

Describe the problem

BugGrabber only has one .zip file on CurseForge with a single .toc containing ## Interface: 90005 (retail). If there were three .toc files, !BugGrabber.toc, !BugGrabber-bcc.toc, and !BugGrabber-classic.toc, with the ## Interface: set appropriately in each, then BugGrabber would be up-to-date on all three versions of WoW automagically. This is a new feature from Blizzard that I don't think has been widely publicized. See https://www.wowinterface.com/forums/showthread.php?t=58747&highlight=multiple+toc+files.

In these uncertain times just after Blizzard has released Burning Crusade Classic, Blizzard wants to disable all out of date addons. Clicking Load Anyway will fix BugGrabber, but also allow any other addons that have not been updated to load potentially causing all sorts of errors.

What steps will reproduce the problem?

1. Install BugSack and BugGrabber on all three flavors of WoW
2. BugGrabber is out-of-date on BCC
3. BugGrabber is out-of-date on Classic
4. BugGrabber is completely operational on Retail

Consider attaching a screenshot below to help describe your issue (Attach directly, do not link to other websites)

What version of the addon are you using? (Stating 'latest' is not useful)

v9.0.2 dated March 27, 2021.

Do you have an error log of what happened?

N/A

Any additional information? (example: WoW language if not English)

Alternate Plan B would be to publish three versions of BugGrabber just like BugSack.

Not so much a problem, but very often I have errors pertaining to Raidcompactframe/tried to call the protected function that don't seem to do much but would be nice to sorta 'ignore'.

Bugsack automatically swaps to the error page for any new errors that come in. Especially during prepatch, when I'm trying to debug and find fixes for a bunch of my addons while waiting for the authors to get everything up to date, it can be incredibly annoying to constantly have the window swapping back to one of the errors if it is firing regularly, when I'm trying to debug a completely different error/addon. It'd be nice if there was an option to disable this behavior.

i get this same error over and over. Any idea?

5x wMarker\config.lua:745: Attempt to register unknown event "PARTY_MEMBERS_CHANGED"
[string "=[C]"]: in function `RegisterEvent'
[string "@wmarker\config.lua"]:745: in main chunk

Locals:
(*temporary) = {
0 =
}
(*temporary) = "PARTY_MEMBERS_CHANGED"

Wasn't sure where to put requests, if you take them. So I'll post it here.

It would be absolutely wonderful if when we pull up the bugsack (/bugsack show) if there was a "wipe bugs" button to use. That way we don't have to do "/bugsack show" and then "/bugsack" again to hit the "wipe saved bugs" button.
I know that you actually have to /reload and/or fix the bugs or uninstall the addon causing the bugs... all that stuff.
But a "wipe bugs" button on the actual window would be totally great and super useful. Please consider this for a future update.

After fighting rares on Mac'aree I'm getting this error, not sure if it belongs to you, or elvui. I'll post below so you can tell me.

2x [ADDON_ACTION_BLOCKED] AddOn 'ElvUI' tried to call the protected function 'MainMenuBar:SetPoint()'.
!BugGrabber\BugGrabber.lua:593: in function <!BugGrabber\BugGrabber.lua:593>
[C]: in function SetPoint' FrameXML\UIParent.lua:2943: in function UIParentManageFramePositions'
FrameXML\UIParent.lua:2326: in function <FrameXML\UIParent.lua:2313>
[C]: in function SetAttribute' FrameXML\UIParent.lua:3115: in function <FrameXML\UIParent.lua:3113> [C]: in function UIParent_ManageFramePositions'
...ns\Blizzard_TalkingHeadUI\Blizzard_TalkingHeadUI.lua:20: in function <...ns\Blizzard_TalkingHeadUI\Blizzard_TalkingHeadUI.lua:19>
[C]: ?
[C]: in function `Hide'
...ns\Blizzard_TalkingHeadUI\Blizzard_TalkingHeadUI.lua:305: in function <...ns\Blizzard_TalkingHeadUI\Blizzard_TalkingHeadUI.lua:304>

Locals:
InCombatSkipped

it didn't start showing up until yesterday.......

It would be nice if BugSack and BugGrabber could be made available for wow classic on curseforge.

Both addons work fine, you just need to upload version for Classic and change the toc to Interface: 11304

When a bug does occur, maybe add a feature for the user to ignore future occurrence of that bug.

Hi wanted to let you know when you click on the npcs in the Artificer Xy' mox fight Hekili doesn't seem to work or it will show buttons to push but only rarely but clicking on Artificer Xy' mox it shows. Wasn't sure if you knew about that or not but I don't have a screenshot to show it.

Since updating to v8.0.1 of buggrabber, I'm getting errors that look like this:

3x Couldn't open TellMeWhen_Options
!BugGrabber\BugGrabber.lua:578: in function <!BugGrabber\BugGrabber.lua:578>

Locals:
nil

4x Error loading BonusRollPreview\libs\Wasabi\LibStub\LibStub-1.0.2-70000.lua
!BugGrabber\BugGrabber.lua:578: in function <!BugGrabber\BugGrabber.lua:578>

Locals:
nil

I can't tell if this is an issue with buggrabber, or with the addons it's posting errors about, because I'm not terribly good at this. But it kind of looks to me like it's an issue wiht line 578 of buggrabber.lua? Sorry if I'm posting in the wrong place.

118x Couldn't open ElvUI
!BugGrabber\BugGrabber.lua:578: in function <!BugGrabber\BugGrabber.lua:578>

20x Deferred XML Node object named Lib_UIDropDownListTemplate already exists
!BugGrabber\BugGrabber.lua:578: in function <!BugGrabber\BugGrabber.lua:578>

20x Deferred XML Node object named Lib_UIDropDownMenuTemplate already exists
!BugGrabber\BugGrabber.lua:578: in function <!BugGrabber\BugGrabber.lua:578>

38x Deferred XML Node object named Lib_UIDropDownMenuButtonTemplate already exists
!BugGrabber\BugGrabber.lua:578: in function <!BugGrabber\BugGrabber.lua:578>

Go to line 313 and change:
searchBox = CreateFrame("EditBox", nil, window)
to
searchBox = CreateFrame("EditBox", nil, window, BackdropTemplateMixin and "BackdropTemplate")

Go to line 323 and change:
edgeSize = 0,
to
edgeSize = 1,

I'd like to be able to opt out of seeing the dialog that pops up on some errors asking me if I'd like to ignore it or disable the addon responsible. I always want to ignore.

Splitting stacks of items in my bags has a tendency to to throw an error that is blamed on Ace3 and turning that off is going to cause a few more problems than it fixes.

Describe the problem

Humbly request a toggle to use the Master audio channel.

216x SharedXML\SharedUIPanelTemplates.lua:672: Attempt to access forbidden object from code tainted by an AddOn
[C]: in function IsOwned' SharedXML\SharedUIPanelTemplates.lua:672: in function PanelTemplates_SelectTab'
BugSack\sack.lua:118: in function <BugSack\sack.lua:32>
BugSack\sack.lua:445: in function <BugSack\sack.lua:440>
BugSack\sack.lua:464: in function OpenSack' BugSack\core.lua:59: in function <BugSack\core.lua:46> [string "safecall Dispatcher[2]"]:4: in function <[string "safecall Dispatcher[2]"]:4> [C]: ? [string "safecall Dispatcher[2]"]:13: in function ?'
...ist\libs\CallbackHandler-1.0\CallbackHandler-1.0-6.lua:90: in function Fire' !BugGrabber\BugGrabber.lua:149: in function <!BugGrabber\BugGrabber.lua:147> !BugGrabber\BugGrabber.lua:370: in function <!BugGrabber\BugGrabber.lua:292> ... [C]: ? [string "safecall Dispatcher[3]"]:13: in function ?'
...ist\libs\CallbackHandler-1.0\CallbackHandler-1.0-6.lua:90: in function Fire' ...s\AckisRecipeList\libs\AceEvent-3.0\AceEvent-3.0-4.lua:120: in function <...s\AckisRecipeList\libs\AceEvent-3.0\AceEvent-3.0.lua:119> [C]: in function UseAction'
FrameXML\SecureTemplates.lua:346: in function handler' FrameXML\SecureTemplates.lua:619: in function SecureActionButton_OnClick'
FrameXML\ActionButton.lua:100: in function <FrameXML\ActionButton.lua:94>
FrameXML\ActionButton.lua:136: in function `ActionButtonDown'
[string "ACTIONBUTTON2"]:2: in function <[string "ACTIONBUTTON2"]:1>

No idea what is wrong with it but BugSack reports me an Error:

2x BugSack\Libs\AceComm-3.0\ChatThrottleLib-23.nil.lua:216: hooksecurefunc(): SendAddonMessage is not a function
[C]: in function hooksecurefunc' BugSack\Libs\AceComm-3.0\ChatThrottleLib-23.nil.lua:216: in function Init'
BugSack\Libs\AceComm-3.0\ChatThrottleLib-23.nil.lua:512: in main chunk

Locals:

Describe the problem

Blizzard's message about a new version of WoW will disable any addon that doesn't have an up-to-date .toc file, i.e. "##Interface: 20501".

BugSack has been fixed but !BugGrabber needs one as well.

What steps will reproduce the problem?

1. Download current versions of BugSack (for BCC) and !BugGrabber (only one version available).
2. Start WoW BCC
3. Let WoW disable obsolete addons.
4. Find a bug

Consider attaching a screenshot below to help describe your issue (Attach directly, do not link to other websites)

What version of the addon are you using? (Stating 'latest' is not useful)

BugSack 9.0.3 with "## Interface: 20501"
!BugGrabber 9.0.2 with "## Interface: 90005"

Do you have an error log of what happened?

No

Any additional information? (example: WoW language if not English)

Changing the .toc file fixes the issue.