298 - PTR 3.3 Build 10554 Interface\AddOns\XPerl\XPerl.lua:1427: bad argument #1 to 'pairs' (table expected, got nil)
What steps will reproduce the problem?
1. Install addon
2. Make sure addon is only one I have enabled
3. Log onto Premade Mage in Orgrema *delete* *delete* *delete* *delete* Orcrim *delete**delete**delete* That Orc main city
4. Work towards training dummies
5. See other people there doing stuff with the training dummies
6. This error comes up randomly. Doesn't seem to be limited
What is the expected output? What do you see instead?
No funny Lua error box coming up
What version of the product are you using?
Build 343
Do you have an error log of what happened?
Message: Interface\AddOns\XPerl\XPerl.lua:1427 bad argument #1 to 'pairs' (table expected, got nil)
Time: Sat Oct 10 02:34:12 2009
Count: 1427
Stack: [C]: in function `pairs'
Interface\AddOns\XPerl\XPerl.lua:1427 in function `XPerl_CombatFlashSetFrames'
Interface\AddOns\XPerl_Target\XPerl_Target.lua:896 in function <Interface\AddOns\XPerl_Target\XPerl_Target.lua:894
Interface\AddOns\XPerl_Target\XPerl_Target.lua:1223 in function `func'
Interface\AddOns\XPerl_Target\XPerl_Target.lua:1084 in function <Interface\AddOns\XPerl_Target\XPerl_Target.lua:1081
Locals: (*temporary) = nil
(*temporary) = "table expected, got nil"
= <function> defined =[C]:-1
Please provide any additional information below.
When I move away from the Combat Dummies this error does not come up again. Attempted to use an event trace but the times did not match the combat log or error report above. Attaching zip of my logs folder.
| Name | Size | MD5 |
|---|---|---|
| Logs.zip | 213.4 KiB | 940fc73b5335... |
- 1 comment
- 1 comment
Facts
- Last updated
- Oct 13, 2009
- Reported
- Oct 09, 2009
- Status
- Declined - We decided not to take action on this ticket.
- Type
- Defect - A shortcoming, fault, or imperfection
- Priority
- Medium - Normal priority.
- Votes
- 0
- Reply
- #1
Zeksie Oct 13, 2009 at 00:22 UTC - 0 likesHave logged on with alpha X-Perl and this doesn't happen. Can only assume it was caused by the other error mentioned causing an incomplete startup.