Hmmm one thing I noticed is that with the extended bug reports if you have auto chat frame output the bug report often exceeds the size of the frame. Which can look a bit ugly.
It would be nice to have a verbose mode and a simple mode (whether the just the first line of the bug is displayed or not). Although that may result in users only reporting the first line :/ perhaps that should be for chat output only, the window should always be verbose.
I don't really think we should worry about makeing bug reports look pretty, they're bugs after all :P It's far more important that they are informative. If you don't like all the spam just turn the chat frame output off.
The short output telling you that an error has been record should be all you really need.
OK, I think I fixed that last reported error locally but unfortunately I'm unable to test ingame until tomorrow at the earliest, so please bear with me until then (a lot of planned RL events this weekend).
scae: I agree with Kyahx here, for normal playing you don't need the full chat frame output, just a simple message.
Phanx: I hope the silence means that you haven't seen a freeze anymore?
My short TODO-list right now:
- check the fix for the BugSackFu error
- fix the frame scale, it's way too big at UI scale 0.64 right now
- check whether BugSackFu really runs without FuBar (it should attach to the minimap)
Anything else to be done? Suggestions? (note that I can't promise when I'll do stuff :-) )
Put the Previous and Next buttons side by side... and the Frist and Last side by side.
If your scrolling through errors when you have gotten a massive spam of them... its a little weird to have to jump across the frame just to skip back one.
Its just a comfort feature, nothing more.... otherwise all is working well.
scae: I agree with Kyahx here, for normal playing you don't need the full chat frame output, just a simple message.
Fair enough, it does make the auto-chat-output kinda pointless though. I would expect anyone to turn it of as the report is larger than the chatframe (default chat frame anyway).
Fair enough, it does make the auto-chat-output kinda pointless though. I would expect anyone to turn it of as the report is larger than the chatframe (default chat frame anyway).
Not really, when I'm working on something thats spitting out alot of errors I make my chat frame as big as possible. Shrink it back down and turn the output off when I'm trying to play the game :P
Chatframe output is nice when your trying to heavily debug something (trial and error seems to be the only way I learn :)), but annoying when you're trying to play.
I would expect everyone to have it off anyways, seeing as it's off by default :P
Chatframe output is nice when your trying to heavily debug something (trial and error seems to be the only way I learn), but annoying when you're trying to play.
I would expect everyone to have it off anyways, seeing as it's off by default
Hah! Ok, that makes perfect sense :) I'm not going to whine about it anymore :P
If the same error occurs multiple times, can BugSack not spam the chat from with multiple error messages? One notice for each unique error should be sufficient, not every instance of the same error.
Or is there a way to turn off chat frame notification?
-- Command descriptions
["Show sack"] = "\232\174\176\229\189\149",
["Show errors in the sack."] = "\230\152\190\231\164\186\232\174\176\229\189\149\233\148\153\232\175\175",
["Current error"] = "\229\189\147\229\137\141\233\148\153\232\175\175",
["Show the current error."] = "\230\152\190\231\164\186\229\189\147\229\137\141\233\148\153\232\175\175",
["Current session"] = "\229\189\147\229\137\141\232\191\155\231\168\139",
["Show errors from the current session."] = "\230\152\190\231\164\186\229\189\147\229\137\141\232\191\155\231\168\139\233\148\153\232\175\175",
["Previous session"] = "\228\184\138\228\184\128\232\191\155\231\168\139",
["Show errors from the previous session."] = "\230\152\190\231\164\186\228\184\138\228\184\128\232\191\155\231\168\139\233\148\153\232\175\175",
["By session number"] = "\232\191\155\231\168\139\230\149\176",
["Show errors by session number."] = "\230\160\185\230\141\174\232\191\155\231\168\139\233\148\153\232\175\175\230\149\176\230\152\190\231\164\186.",
["All errors"] = "\229\133\168\233\131\168\233\148\153\232\175\175",
["Show all errors."] = "\230\152\190\231\164\186\229\133\168\233\131\168\233\148\153\232\175\175.",
["List errors"] = "\229\136\151\228\184\190\233\148\153\232\175\175",
["List errors to the chat frame."] = "\229\156\168\232\129\138\229\164\169\230\161\134\229\136\151\229\135\186\233\148\153\232\175\175.",
["List the current error."] = "\229\136\151\229\135\186\229\189\147\229\137\141\233\148\153\232\175\175.",
["List errors from the current session."] = "\229\136\151\229\135\186\229\189\147\229\137\141\232\191\155\231\168\139\233\148\153\232\175\175.",
["List errors from the previous session."] = "\229\136\151\229\135\186\228\184\138\228\184\128\232\191\155\231\168\139\233\148\153\232\175\175",
["List errors by session number."] = "\229\136\151\229\135\186\232\191\155\231\168\139\233\148\153\232\175\175\230\149\176.",
["List all errors."] = "\229\136\151\229\135\186\229\133\168\233\131\168\233\148\153\232\175\175.",
["Auto popup"] = "\232\135\170\229\138\168\229\188\185\229\135\186",
["Toggle auto BugSack frame popup."] = "\233\129\135\229\136\176\233\148\153\232\175\175\230\152\175\229\144\166\232\135\170\229\138\168\229\188\185\229\135\186 BugSack \231\170\151\229\143\163",
["Auto chat output"] = "\232\135\170\229\138\168\232\129\138\229\164\169\232\190\147\229\135\186",
["Toggle auto printing of messages to the chat frame."] = "\229\136\135\230\141\162\232\129\138\229\164\169\231\170\151\229\143\163\232\190\147\229\135\186\233\148\153\232\175\175\228\191\161\230\129\175.",
["Mute"] = "\233\157\153\233\159\179",
["Toggle an audible warning everytime an error occurs."] = "\229\136\135\230\141\162\233\148\153\232\175\175\229\143\145\231\148\159\230\151\182\229\143\145\229\135\186\232\173\166\229\145\138\229\163\176.",
["Save errors"] = "\228\191\157\229\173\152\233\148\153\232\175\175",
["Toggle whether to save errors to your SavedVariables\\!BugGrabber.lua file."] = "\230\152\175\229\144\166\229\156\168 SavedVariables\\!BugGrabber.lua \230\150\135\228\187\182\228\184\173\228\191\157\229\173\152\233\148\153\232\175\175\228\191\161\230\129\175",
["Limit"] = "\233\153\144\229\136\182",
["Set the limit on the nr of errors saved."] = "\232\174\190\231\189\174\233\148\153\232\175\175\228\191\157\229\173\152\233\153\144\229\136\182",
["Generate bug"] = "\230\168\161\230\139\159\233\148\153\232\175\175",
["Generate a fake bug for testing."] = "\230\168\161\230\139\159\228\186\167\231\148\159\228\184\128\228\184\170\230\168\161\230\139\159\233\148\153\232\175\175\232\191\155\232\161\140\230\181\139\232\175\149.",
["Script bug"] = "\232\132\154\230\156\172\233\148\153\232\175\175",
["Generate a script bug."] = "\230\168\161\230\139\159\228\186\167\231\148\159\228\184\128\228\184\170\232\132\154\230\156\172\233\148\153\232\175\175.",
["Addon bug"] = "\230\143\146\228\187\182\231\188\186\233\153\183",
["Generate an addon bug."] = "\230\168\161\230\139\159\228\186\167\231\148\159\228\184\128\228\184\170\230\143\146\228\187\182\231\188\186\233\153\183.",
["Clear errors"] = "\230\184\133\233\153\164\233\148\153\232\175\175",
["Clear out the errors database."] = "\230\184\133\233\153\164\233\148\153\232\175\175\230\149\176\230\141\174\229\186\147.",
-- Chat messages
["You have no errors, yay!"] = "\230\178\161\230\156\137\229\143\145\231\148\159\233\148\153\232\175\175, \\^o^/",
["List of errors:"] = "\233\148\153\232\175\175\229\136\151\232\161\168",
["An error has been generated."] = "",
["BugSack generated this fake error."] = "BugSack \228\186\167\231\148\159\230\173\164\230\168\161\230\139\159\233\148\153\232\175\175.",
["All errors were wiped."] = "\230\137\128\230\156\137\233\148\153\232\175\175\232\162\171\230\184\133\233\153\164.",
["An error has been recorded."] = "\230\137\128\230\156\137\233\148\153\232\175\175\232\162\171\232\174\176\229\189\149.",
-- FuBar plugin
["Click to open the BugSack frame with the last error."] = "\231\130\185\229\135\187\230\159\165\231\156\139\232\174\176\229\189\149\231\154\132\230\156\128\229\144\142\228\184\128\228\184\170\233\148\153\232\175\175.",
}
end)
Had a looping error with a mod, which caused a bunch of entries in !BugGrabber.lua
Then for some reason, WoW would crash every time I tried to reload or logout. I narrowed it down to the !BugGrabber.lua in my SavedVariables, which is attached.
Hope this helps, was fairly tough to nail down the problem file.
thomasmo: thanks for the translation, I'll check it into the SVN as soon as possible!
Devla: Many thanks for the report! I can now finally reproduce the crash on reload. I do not however see something very wrong in !BugGrabber, but at least now I can try to narrow it down to something in that file. However because of it's unobviousness, I can't give an ETA to the fix yet :-/ I'll try to fix it as soon as possible however.
Sent: I doubt that it's my plugin doing that, are you still seeing this after updating FuBar?
teedog: I don't know about supressing duplicate errors, because sometimes it is very relevant to a developer to know how many times a certain error occurred (IE for every person in a raid, or just for the pets?). Still, I'm debating adding a 'totally silent' mode that won't spam the chat frame nor make a sound. Now that the FuBar plugin shows the nr of errors I guess it's not as necessary anymore to output to the chat frame anyway. Will that do?
teedog: I don't know about supressing duplicate errors, because sometimes it is very relevant to a developer to know how many times a certain error occurred (IE for every person in a raid, or just for the pets?). Still, I'm debating adding a 'totally silent' mode that won't spam the chat frame nor make a sound. Now that the FuBar plugin shows the nr of errors I guess it's not as necessary anymore to output to the chat frame anyway. Will that do?
As an end-user, yep I like the idea of a silent mode. I can report how many duplicate errors I get from looking at the FuBar plugin. The error messages to the chat frame can spam so much it fills half the chat buffer and makes important whispers or other info scroll past.
OK, I just found the cause of the crashes -- it seems WoW has an internal limit on the size of strings in the SavedVariables\*.lua files, and one of your bug messages was longer than that. I've put in a guard against such long messages in !BugGrabber, but you will have to delete your old SavedVariables\!BugGrabber.lua if you're currently suffering this bug (it doesn't make sense to put in scanning / fixing code for this edgecase so that everyone's load times will suffer from BugGrabber's over zealous fixing of messages that in 99.9% of the cases are fine anyway).
So, be sure to update to the latest SVN to prevent this from happening in the future. Thanks again for the nice report, Devla! And definitely no cookie for Blizzard for not having a guard against this kind of thing in their saving/loading code.
Oh and thomasmo, I added your zhCN translation to the repository, please check if I did that correctly because I have no way of testing it :)
As a regular end-user (and not a dev), I must say that I love this version.
It's easy to check the errors, clean them, list them... you name it.
Definitly a must have ^^
Rollback Post to RevisionRollBack
To post a comment, please login or register a new account.
It would be nice to have a verbose mode and a simple mode (whether the just the first line of the bug is displayed or not). Although that may result in users only reporting the first line :/ perhaps that should be for chat output only, the window should always be verbose.
The short output telling you that an error has been record should be all you really need.
scae: I agree with Kyahx here, for normal playing you don't need the full chat frame output, just a simple message.
Phanx: I hope the silence means that you haven't seen a freeze anymore?
My short TODO-list right now:
- check the fix for the BugSackFu error
- fix the frame scale, it's way too big at UI scale 0.64 right now
- check whether BugSackFu really runs without FuBar (it should attach to the minimap)
Anything else to be done? Suggestions? (note that I can't promise when I'll do stuff :-) )
Put the Previous and Next buttons side by side... and the Frist and Last side by side.
If your scrolling through errors when you have gotten a massive spam of them... its a little weird to have to jump across the frame just to skip back one.
Its just a comfort feature, nothing more.... otherwise all is working well.
Fair enough, it does make the auto-chat-output kinda pointless though. I would expect anyone to turn it of as the report is larger than the chatframe (default chat frame anyway).
Not really, when I'm working on something thats spitting out alot of errors I make my chat frame as big as possible. Shrink it back down and turn the output off when I'm trying to play the game :P
Chatframe output is nice when your trying to heavily debug something (trial and error seems to be the only way I learn :)), but annoying when you're trying to play.
I would expect everyone to have it off anyways, seeing as it's off by default :P
Hah! Ok, that makes perfect sense :) I'm not going to whine about it anymore :P
I get that too. Though strangely is also applies to squishy and bigwigs as well. Figured it was a FuBar error.... *goes to update from SVN*..
!BugGrabber has to be loaded first, you can't load bugGrabber First if it has ace2 and libs as a dependancy.
Or is there a way to turn off chat frame notification?
there is for CWOW local file
-- by Thomas Mo
local L = AceLibrary("AceLocale-2.0"):new("BugSack")
L:RegisterTranslations("zhCN", function()
return {
-- Bindings
["Show Current Error"] = "\230\152\190\231\164\186\229\189\147\229\137\141\233\148\153\232\175\175",
["Show Session Errors"] = "\230\152\190\231\164\186\232\191\155\231\168\139\233\148\153\232\175\175",
-- Command descriptions
["Show sack"] = "\232\174\176\229\189\149",
["Show errors in the sack."] = "\230\152\190\231\164\186\232\174\176\229\189\149\233\148\153\232\175\175",
["Current error"] = "\229\189\147\229\137\141\233\148\153\232\175\175",
["Show the current error."] = "\230\152\190\231\164\186\229\189\147\229\137\141\233\148\153\232\175\175",
["Current session"] = "\229\189\147\229\137\141\232\191\155\231\168\139",
["Show errors from the current session."] = "\230\152\190\231\164\186\229\189\147\229\137\141\232\191\155\231\168\139\233\148\153\232\175\175",
["Previous session"] = "\228\184\138\228\184\128\232\191\155\231\168\139",
["Show errors from the previous session."] = "\230\152\190\231\164\186\228\184\138\228\184\128\232\191\155\231\168\139\233\148\153\232\175\175",
["By session number"] = "\232\191\155\231\168\139\230\149\176",
["Show errors by session number."] = "\230\160\185\230\141\174\232\191\155\231\168\139\233\148\153\232\175\175\230\149\176\230\152\190\231\164\186.",
["All errors"] = "\229\133\168\233\131\168\233\148\153\232\175\175",
["Show all errors."] = "\230\152\190\231\164\186\229\133\168\233\131\168\233\148\153\232\175\175.",
["List errors"] = "\229\136\151\228\184\190\233\148\153\232\175\175",
["List errors to the chat frame."] = "\229\156\168\232\129\138\229\164\169\230\161\134\229\136\151\229\135\186\233\148\153\232\175\175.",
["List the current error."] = "\229\136\151\229\135\186\229\189\147\229\137\141\233\148\153\232\175\175.",
["List errors from the current session."] = "\229\136\151\229\135\186\229\189\147\229\137\141\232\191\155\231\168\139\233\148\153\232\175\175.",
["List errors from the previous session."] = "\229\136\151\229\135\186\228\184\138\228\184\128\232\191\155\231\168\139\233\148\153\232\175\175",
["List errors by session number."] = "\229\136\151\229\135\186\232\191\155\231\168\139\233\148\153\232\175\175\230\149\176.",
["List all errors."] = "\229\136\151\229\135\186\229\133\168\233\131\168\233\148\153\232\175\175.",
["Auto popup"] = "\232\135\170\229\138\168\229\188\185\229\135\186",
["Toggle auto BugSack frame popup."] = "\233\129\135\229\136\176\233\148\153\232\175\175\230\152\175\229\144\166\232\135\170\229\138\168\229\188\185\229\135\186 BugSack \231\170\151\229\143\163",
["Auto chat output"] = "\232\135\170\229\138\168\232\129\138\229\164\169\232\190\147\229\135\186",
["Toggle auto printing of messages to the chat frame."] = "\229\136\135\230\141\162\232\129\138\229\164\169\231\170\151\229\143\163\232\190\147\229\135\186\233\148\153\232\175\175\228\191\161\230\129\175.",
["Mute"] = "\233\157\153\233\159\179",
["Toggle an audible warning everytime an error occurs."] = "\229\136\135\230\141\162\233\148\153\232\175\175\229\143\145\231\148\159\230\151\182\229\143\145\229\135\186\232\173\166\229\145\138\229\163\176.",
["Save errors"] = "\228\191\157\229\173\152\233\148\153\232\175\175",
["Toggle whether to save errors to your SavedVariables\\!BugGrabber.lua file."] = "\230\152\175\229\144\166\229\156\168 SavedVariables\\!BugGrabber.lua \230\150\135\228\187\182\228\184\173\228\191\157\229\173\152\233\148\153\232\175\175\228\191\161\230\129\175",
["Limit"] = "\233\153\144\229\136\182",
["Set the limit on the nr of errors saved."] = "\232\174\190\231\189\174\233\148\153\232\175\175\228\191\157\229\173\152\233\153\144\229\136\182",
["Generate bug"] = "\230\168\161\230\139\159\233\148\153\232\175\175",
["Generate a fake bug for testing."] = "\230\168\161\230\139\159\228\186\167\231\148\159\228\184\128\228\184\170\230\168\161\230\139\159\233\148\153\232\175\175\232\191\155\232\161\140\230\181\139\232\175\149.",
["Script bug"] = "\232\132\154\230\156\172\233\148\153\232\175\175",
["Generate a script bug."] = "\230\168\161\230\139\159\228\186\167\231\148\159\228\184\128\228\184\170\232\132\154\230\156\172\233\148\153\232\175\175.",
["Addon bug"] = "\230\143\146\228\187\182\231\188\186\233\153\183",
["Generate an addon bug."] = "\230\168\161\230\139\159\228\186\167\231\148\159\228\184\128\228\184\170\230\143\146\228\187\182\231\188\186\233\153\183.",
["Clear errors"] = "\230\184\133\233\153\164\233\148\153\232\175\175",
["Clear out the errors database."] = "\230\184\133\233\153\164\233\148\153\232\175\175\230\149\176\230\141\174\229\186\147.",
-- Chat messages
["You have no errors, yay!"] = "\230\178\161\230\156\137\229\143\145\231\148\159\233\148\153\232\175\175, \\^o^/",
["List of errors:"] = "\233\148\153\232\175\175\229\136\151\232\161\168",
["An error has been generated."] = "",
["BugSack generated this fake error."] = "BugSack \228\186\167\231\148\159\230\173\164\230\168\161\230\139\159\233\148\153\232\175\175.",
["All errors were wiped."] = "\230\137\128\230\156\137\233\148\153\232\175\175\232\162\171\230\184\133\233\153\164.",
["An error has been recorded."] = "\230\137\128\230\156\137\233\148\153\232\175\175\232\162\171\232\174\176\229\189\149.",
-- Frame messages,
[" (... more ...)"] = "(... \230\155\180\229\164\154...)",
["No errors found"] = "\230\156\170\229\143\145\231\142\176\233\148\153\232\175\175",
["Error %d of %d"] = "\233\148\153\232\175\175 %d/%d",
[" (viewing last error)"] = " (\230\159\165\231\156\139\230\156\128\229\144\142\228\184\128\228\184\170\233\148\153\232\175\175)",
[" (viewing session errors)"] = " (\230\159\165\231\156\139\230\173\164\230\172\161\232\191\155\231\168\139\233\148\153\232\175\175)",
[" (viewing previous session errors)"] = " (\230\159\165\231\156\139\228\184\138\228\184\128\232\191\155\231\168\139\233\148\153\232\175\175)",
[" (viewing all errors)"] = " (\230\159\165\231\156\139\229\133\168\233\131\168\233\148\153\232\175\175)",
[" (viewing errors for session %d)"] = " (\230\159\165\231\156\139 \"%d\" \232\191\155\231\168\139\233\148\153\232\175\175)",
-- FuBar plugin
["Click to open the BugSack frame with the last error."] = "\231\130\185\229\135\187\230\159\165\231\156\139\232\174\176\229\189\149\231\154\132\230\156\128\229\144\142\228\184\128\228\184\170\233\148\153\232\175\175.",
}
end)
BugSackNextButton:SetText("\228\184\139\228\184\128\228\184\170")
BugSackLastButton:SetText("\230\156\128\229\144\142")
BugSackPrevButton:SetText("\228\184\138\228\184\128\228\184\170")
BugSackFirstButton:SetText("\230\156\128\229\136\157")
Then for some reason, WoW would crash every time I tried to reload or logout. I narrowed it down to the !BugGrabber.lua in my SavedVariables, which is attached.
Hope this helps, was fairly tough to nail down the problem file.
Devla: Many thanks for the report! I can now finally reproduce the crash on reload. I do not however see something very wrong in !BugGrabber, but at least now I can try to narrow it down to something in that file. However because of it's unobviousness, I can't give an ETA to the fix yet :-/ I'll try to fix it as soon as possible however.
Sent: I doubt that it's my plugin doing that, are you still seeing this after updating FuBar?
teedog: I don't know about supressing duplicate errors, because sometimes it is very relevant to a developer to know how many times a certain error occurred (IE for every person in a raid, or just for the pets?). Still, I'm debating adding a 'totally silent' mode that won't spam the chat frame nor make a sound. Now that the FuBar plugin shows the nr of errors I guess it's not as necessary anymore to output to the chat frame anyway. Will that do?
As an end-user, yep I like the idea of a silent mode. I can report how many duplicate errors I get from looking at the FuBar plugin. The error messages to the chat frame can spam so much it fills half the chat buffer and makes important whispers or other info scroll past.
So, be sure to update to the latest SVN to prevent this from happening in the future. Thanks again for the nice report, Devla! And definitely no cookie for Blizzard for not having a guard against this kind of thing in their saving/loading code.
Oh and thomasmo, I added your zhCN translation to the repository, please check if I did that correctly because I have no way of testing it :)
It's easy to check the errors, clean them, list them... you name it.
Definitly a must have ^^