Randomly (couldn't notice a specific cause so far) during combat:
[2007/11/25 01:55:53-161-x1]: AceComm-2.0-49773 (Ace2):344: bad argument #1 to 'string_char' (invalid value)
Similar error here with AceComm-2.0 last night:
AceComm-2.0-56239 (Ace2):307: bad argument #1 to 'string_char' (invalid value)
. Using the further modified r56239 as noted in the error message (lastest as of this date).
Like the parent poster, the error also happened when I was in a 10-person raid group (for Kara); first raid group I was in since AceComm-2.0 started to be modified on Nov 27 (r56100). Popped up sometime during combat. Never happened in 5-person runs prior to that.
Don't know an exact way to reproduce the it, other than getting in a full raid group and playing in combat for a while. This error never occurred in raids or elsewhere using AceComm-2.0 r50175 or earlier. But seeing as its the identical code in the two revisions where the error is happening with both myself and the parent poster (who was using the earlier r49773 from September):
function EncodeBytes(drunk, ...)
return string_char(EncodeBytes_helper(drunk, ...))
its likely a deeper rooted problem :(. Doesn't explain why I've never seen this error before, though.
Like the parent poster, the error also happened when I was in a 10-person raid group (for Kara); first raid group I was in since AceComm-2.0 started to be modified on Nov 27 (r56100).
And yet, the error occurs in AceComm-2.0 revisions before Nov 27 as well, the changes since then has had no effect on this bug, and they have just been cleanups, no functionality changes or bug fixes.
I'm guessing it's an issue surfaced from patch 2.3, or some addon that does something it shouldn't do.
Since the 2.3 patch I have been getting this error message every time I join a group. The only addon (That I'm glaringly aware of, apart from perhaps PitBull) that is activated when I join a group is Omen. Now I'll probably get 100 people saying "I don't have this issue with Omen..." Which is fine. I do. Or could it be Threat 1.0? I don't know. But it occurs every single time I join a group then attack something.
AceComm-2.0-56239 (Ace2):307: bad argument #1 to 'string_char' (invalid value)
When the error happens, the people who were displaying on Omen then disappear and it's only me on there.
Aye, I've been trying to figure out what is causing it too. I guess I'm gonna have to do the turn-off all addons thing sometime soon. There is an addon it doesn't like I'm sure of it because I have a few buddies who are not getting this bug at all.
The stack traces are a bit off for AceComm-2.0.lua because I added some lines of debug to it, but the Parser-4.0 and Threat-1.0 lines should be accurate.
Note that numerical codes are not necessarily portable across platforms.
Stan_ on IRC mentioned getting this error and when I asked he said he was using Vista with everything set to German and WoW in enGB. But as we all should know, Lua isn't unicode and WoW translations are just locale files so his WoW is still running on a German codepage. I'm willing to bet that somehow this is related because I have never gotten this error and nobody in my guild has ever mentioned getting this error and we're all American or Canadian (a few French Canadians but I have no clue what locale their Windows is in).
Has anybody who's gotten this error mentioned what codepage is being used for non-unicode programs on their computer? I think it would be a good idea to start asking and if somebody answers "English (United States)" then we'll know this probably isn't related to codepages.
EDIT: Stan_ tested "t={} for i = 1, 255 do table.insert(t, i) end return string.char(unpack(t))" and no error so probably safe to disregard my wild theory.
EDIT2: "312 [306] SETGLOBAL 99 -135 ; EncodeBytes" in AceComm-2.0.lua, fix please then slap ckknight and figure out wtf these are suppost to be....
"451 [1062] GETGLOBAL 12 -35 ; finish"
"468 [1066] GETGLOBAL 13 -35 ; finish"
I traced a BIG FAT BUG in AceComm to the following function
local function GetCurrentGroupDistribution()
if MiniMapBattlefieldFrame.status == "active" then
return "BATTLEGROUND"
elseif UnitInRaid("player") then
return "RAID"
else
return "PARTY"
end
end
It should not be using MiniMapBattlefieldFrame.status to check, it should be using IsInInstance(). tekMapEnhancer and the 2.3 changes to make the Battle Map usable in any zone breaks Omen by trying to send to threat data to the "BATTLEGROUD" distribution if the zone map is active.
Line 1125: return MiniMapBattlefieldFrame.status == "active"
After a little checking of the mod Bongos Skinned Map which was reported to be breaking Threat-1.0 for unknown reasons, I found that version 5.1 was setting MiniMapBattlefieldFrame.status = "active" but version 6 and latter weren't. So that untraceable bug was caused by this one.
57139 created by antiarc on 18 December 2007, 10:35:28 -0800 (28 minutes ago) (patch)
Ace2: Update GetCurrentGroupDistribution() and IsInDistribution() to not rely on the battleground minimap active status to detemine the difference between BATTLEGROUND and RAID distributions. Now uses select(2, IsInInstance()) == "pvp". Addresses [url]http://www.wowace.com/forums/index.php?topic=6419.msg166161#msg166161[/url] and a number of other potential silent comms failures in raid situations.
-
View User Profile
-
View Posts
-
Send Message
Curse Premium-
View User Profile
-
View Posts
-
Send Message
Curse Premium-
View User Profile
-
View Posts
-
Send Message
Curse PremiumHow can we reproduce it?
-
View User Profile
-
View Posts
-
Send Message
Curse PremiumSimilar error here with AceComm-2.0 last night:
. Using the further modified r56239 as noted in the error message (lastest as of this date).
Like the parent poster, the error also happened when I was in a 10-person raid group (for Kara); first raid group I was in since AceComm-2.0 started to be modified on Nov 27 (r56100). Popped up sometime during combat. Never happened in 5-person runs prior to that.
Don't know an exact way to reproduce the it, other than getting in a full raid group and playing in combat for a while. This error never occurred in raids or elsewhere using AceComm-2.0 r50175 or earlier. But seeing as its the identical code in the two revisions where the error is happening with both myself and the parent poster (who was using the earlier r49773 from September):
its likely a deeper rooted problem :(. Doesn't explain why I've never seen this error before, though.
-
View User Profile
-
View Posts
-
Send Message
Curse PremiumAnd yet, the error occurs in AceComm-2.0 revisions before Nov 27 as well, the changes since then has had no effect on this bug, and they have just been cleanups, no functionality changes or bug fixes.
I'm guessing it's an issue surfaced from patch 2.3, or some addon that does something it shouldn't do.
AceComm-2.0-56239 (Ace2):307: bad argument #1 to 'string_char' (invalid value)
When the error happens, the people who were displaying on Omen then disappear and it's only me on there.
-
View User Profile
-
View Posts
-
Send Message
Curse PremiumWill keep you posted.
-
View User Profile
-
View Posts
-
Send Message
Forum Moderator-
View User Profile
-
View Posts
-
Send Message
Curse PremiumHopefully I'll have more details soon.
http://ace.pastey.net/78945
http://ace.pastey.net/78946
The stack traces are a bit off for AceComm-2.0.lua because I added some lines of debug to it, but the Parser-4.0 and Threat-1.0 lines should be accurate.
-
View User Profile
-
View Posts
-
Send Message
Curse Premium-
View User Profile
-
View Posts
-
Send Message
Curse Premium1. You're trying to send a message. Code errored before anything got sent.
2. SendAddonMessage() does not get affected by drunk.
Stan_ on IRC mentioned getting this error and when I asked he said he was using Vista with everything set to German and WoW in enGB. But as we all should know, Lua isn't unicode and WoW translations are just locale files so his WoW is still running on a German codepage. I'm willing to bet that somehow this is related because I have never gotten this error and nobody in my guild has ever mentioned getting this error and we're all American or Canadian (a few French Canadians but I have no clue what locale their Windows is in).
Has anybody who's gotten this error mentioned what codepage is being used for non-unicode programs on their computer? I think it would be a good idea to start asking and if somebody answers "English (United States)" then we'll know this probably isn't related to codepages.
EDIT: Stan_ tested "t={} for i = 1, 255 do table.insert(t, i) end return string.char(unpack(t))" and no error so probably safe to disregard my wild theory.
EDIT2: "312 [306] SETGLOBAL 99 -135 ; EncodeBytes" in AceComm-2.0.lua, fix please then slap ckknight and figure out wtf these are suppost to be....
"451 [1062] GETGLOBAL 12 -35 ; finish"
"468 [1066] GETGLOBAL 13 -35 ; finish"
I do get the error occasionally (in group or raid environment)
My addons that use AceComm are:
- Assessment
- Bidder (part of DKPmon package)
- BugSack
- CraftList2
- GrindStatus
- Omnibus
- SorrenTimers
- WoWEquip
From those at least one cross-references Rabbit's suspicion for Threat-1.0 (as part of Assessment)
-
View User Profile
-
View Posts
-
Send Message
Forum ModeratorWe'll see :)
Thank you ckknight :)
-
View User Profile
-
View Posts
-
Send Message
Curse Premiumlocal function GetCurrentGroupDistribution() if MiniMapBattlefieldFrame.status == "active" then return "BATTLEGROUND" elseif UnitInRaid("player") then return "RAID" else return "PARTY" end endIt should not be using MiniMapBattlefieldFrame.status to check, it should be using IsInInstance(). tekMapEnhancer and the 2.3 changes to make the Battle Map usable in any zone breaks Omen by trying to send to threat data to the "BATTLEGROUD" distribution if the zone map is active.
Line 1125: return MiniMapBattlefieldFrame.status == "active"
is affected as well.
http://www.wowace.com/forums/index.php?topic=6419.msg166161#msg166161
2 posts above this linked post has the full 7 lines of code for tekMapEnhancer.
-
View User Profile
-
View Posts
-
Send Message
Forum ModeratorThanks, Antiarc! :)
-
View User Profile
-
View Posts
-
Send Message
Forum ModeratorNext one! :) Happened while duelling.