Logged Out
Create an Account
Login:
Password:

Forgot your password?
grss program error

grss program error
[Back to Index]  [Bottom of Thread]
Thread Tags
Primary: [Tickets]
Secondary: None
grss program error
Go To This Ticket's Page
Creator budenhagen
Public or Private Public
Private tickets are only accessible to you and to DKPSystem.com staff
Public Tickets are visible to everyone)
Status Open
Type Bug
Section of the Site Game Addons/Importers
Urgency (1 votes)
Rating (1 votes)
Description:
downloaded the new grss snapshot. I get an error:

idSnapshot.lua.227:bad arguement #1 to "find" (string expected got table)

this continually pops up. help
Official DKPSystem.com Comments
No official comments yet
Hm... I'm not able to reproduce this.

When does this error pop up?

The confusion lies in that line 227 of GuildRaidsnapShot.lua isn't making a call to "find", which makes this particular error rather baffling.

--
It's all in the reflexes.
this comes up about every 3 minutes when im in a raid
I am getting the same error when i send myself a tell and use !dkp to see my total score
I'm definitely not able to reproduce the error message popup.

Could I ask what mods you guys are running? Jenfu, in particular, since you're able to reproduce it regularly, my recommendation is to see if another mod is possibly causing the error (This wouldn't be the first time an error from another mod manifested itself in the GRSS). The Whisper system had a pretty significant tweak that broke many mods that accept whispers.

--
It's all in the reflexes.
Quote by Chops
I'm definitely not able to reproduce the error message popup.

Could I ask what mods you guys are running? Jenfu, in particular, since you're able to reproduce it regularly, my recommendation is to see if another mod is possibly causing the error (This wouldn't be the first time an error from another mod manifested itself in the GRSS). The Whisper system had a pretty significant tweak that broke many mods that accept whispers.



Here is a Cut and paste for you Chops.

Date: 2009-04-28 18:08:25
ID: 1
Error occured in: Global
Count: 1
Message: ...rface\AddOns\GuildRaidSnapShot\GuildRaidSnapShot.lua line 227:
bad argument #1 to 'find' (string expected, got table)
Debug:
[C]: ?
[C]: find()
...rface\AddOns\GuildRaidSnapShot\GuildRaidSnapShot.lua:227: filterFunc()
..\FrameXML\ChatFrame.lua:2352: ChatFrame_MessageEventHandler()
..\FrameXML\ChatFrame.lua:2195: ChatFrame_OnEvent()
[string "*:OnEvent"]:1:
[string "*:OnEvent"]:1
AddOns:
Swatter, v5.4.4157 (WallabyII)
Bartender4, v4.3.2
DBMCore, v
DebugLib, v5.1.DEV.130
FuBar, v
FuBarRaidLog, v3.0.2.1
Grid, v1.30100.2009041601
GuildRaidSnapShot, v
Omen, v3.0.7
Quartz, v1.0
QuartzBuff, v1.0
QuartzFlight, v1.0
QuartzFocus, v1.0
QuartzGCD, v1.0
QuartzInterrupt, v1.0
QuartzLatency, v1.0
QuartzMirror, v1.0
QuartzPet, v1.0
QuartzPlayer, v1.0
QuartzRange, v1.0
QuartzSwing, v1.0
QuartzTarget, v1.0
QuartzTimer, v1.0
QuartzTradeskill, v1.0
RatingBuster, v
Recount, v
RollTracker2, v
SlideBar, v5.4.4157 (WallabyII)
Stubby, v5.4.4157 (WallabyII)
Titan, v4.2.1.30100 - Revision 234
TitanAmmo, v4.2.1.30100
TitanBag, v4.2.1.30100
TitanClock, v4.2.1.30100
TitanCoords, v4.2.1.30100
TitanDurability, v1.16
TitanGoldTracker, v4.2.1.30100
TitanLootType, v4.2.1.30100
TitanPerformance, v4.2.1.30100
TitanRaidIds, v2.1.38
TitanRegen, v4.2.1.30100
TitanRepair, v4.2.1.30100
TitanVolume, v4.2.1.30100
TitanXP, v4.2.1.30100
(ck=3f1)

This is going to be a big request, since the trace you've provided still doesn't give me anything to work with. Line 227 of GuildRaidSnapShot isn't a call to string.find.

Could you zip up and post you entire Addons folder? I'm not able to reproduce this at all, but I run pretty much vanilla WoW.

--
It's all in the reflexes.
Jenfu your list doesn't look complete (DBM should be multiple entries for example), and I think you might be running some older addons. Try updating your addons (in addition to sending them to Chops).

Also the problem may be hiding in your WTF folder. Try renaming it or moving it to your desktop temporarily to see if you still have the error after WoW creates a new one.

--


[Back to Index]  [Top of Thread]