WowAce.com

Baggins

109 - Error concatenating string with nil in Baggins-Options

- What steps will reproduce the problem?
It happens pretty frequently for me but I can't reliably reproduce it.

- What is the expected output? What do you see instead?
I get an error in Baggins-Options.lua at line 1954; rulename is nil here for some reason, so when it tries to prefix it with rule.operation there is an error.

- What version of the product are you using?
r473-nolib

- Do you have an error log of what happened?
Not currently, I can provide one if needed.

- Please provide any additional information below.
This has been happening to me for a long time now (years), and I've just been patching it by hand to make the problem go away. I'm guessing it's something nonstandard in my rules that is making Baggins:GetRuleDesc(rule) come back as nil, but I haven't investigated what exactly that is. But the whole block of code from line 1947 to 1955 is pointless; it sets up a local rulename variable which is then never used. So I just always commented out those lines and everything else has been fine. Now that updates are happening more frequently again (thank you!) it's getting annoying to fix it myself every time there's a new release :)

User When Change
Baconslicer Nov 14, 2014 at 19:05 UTC Create

You must login to post a comment. Don't have an account? Register to get one!

  • 2 comments
  • Avatar of Baconslicer Baconslicer Feb 15, 2015 at 18:58 UTC - 0 likes

    @atholbro: Go

    Tested it in the latest alpha, and this seems to be fixed. Thanks!

  • Avatar of atholbro atholbro Jan 31, 2015 at 22:36 UTC - 0 likes

    Yes, you're right that code is pointless. I've removed it, so future updates shouldn't cause this issue.

  • 2 comments

Facts

Reported
Nov 14, 2014
Status
New - Issue has not had initial review yet.
Type
Defect - A shortcoming, fault, or imperfection
Priority
Medium - Normal priority.
Votes
0

Reported by

Possible assignees