shirsig / aux-addon

Auction House addOn for Classic (1.13) IMPORTANT: The folder name must be "aux-addon" IMPORTANT: The Vanilla (1.12) version moved here https://github.com/shirsig/aux-addon-vanilla
https://www.curseforge.com/wow/addons/aux
196 stars 42 forks source link

[lua error] #300

Closed waytoomuchgaming closed 3 years ago

waytoomuchgaming commented 4 years ago

4x aux-addon\tabs\post\core.lua:341: attempt to perform arithmetic on field 'unit_vendor_price' (a nil value) aux-addon\tabs\post\core.lua:341: in function `update_item_configuration' aux-addon\tabs\post\core.lua:563: in function <aux-addon\tabs\post\core.lua:559>

Locals: deposit_factor = 0.050000 duration_factor = 12 stack_size = 1 stack_count = 2 (temporary) = defined =[C]:-1 (temporary) = nil (temporary) = (temporary) = nil (temporary) = nil (temporary) = nil (temporary) = nil (temporary) = nil (temporary) = nil (temporary) = "attempt to perform arithmetic on field 'unit_vendor_price' (a nil value)" aux =

{ } info =
{ } money =
{ }

shirsig commented 4 years ago

Did this appear with the recent update? Any info on how to reproduce? It kind of looks like an old bug that caused corrupted post tab settings. The bug was fixed but corrupted settings might still be there for specific items.

waytoomuchgaming commented 4 years ago

Edit: yes, it was with the last update.

Not sure how to accurately reproduce it. Right now i get it again, it was while posting iron buckles. And they were posted, but i had to close the AH and open it again to see them.

waytoomuchgaming commented 4 years ago

And again with frost oils. I had 6 in my bags, posting 2 stacks of 1.

shirsig commented 4 years ago

can you try /aux clear post to see if the issue reappears afterwards?

waytoomuchgaming commented 4 years ago

I did after you posted your message (2 days ago), and i just got the bug again. With frost oils, again. Again with 6 in my bags, posting 2 stacks of 1.

shirsig commented 4 years ago

Strange, I still haven't ever had it happen.

waytoomuchgaming commented 4 years ago

I got it again, posting dark iron bars. I posted multiple stack size with no problem, and then with one stack of 8, i got the bug.

I have the feeling it can happen when the addon have to make a posting pile from a certain size coming from at least 2 different piles, because nothing of the desired size exist in the bag.

Should i continue to update that bug with the errors i get (it's always the same error, but the items vary) ?

shirsig commented 4 years ago

Yes, please. It's strange because there was a bug with posting a remainder stack with the previous version, though more severe and 100% reproducible, but now I have no issues with it.

If anyone else is reading this and has the same issue please comment as well.

waytoomuchgaming commented 4 years ago

Same error, posting 1 mithril casing (11 in my bag).

waytoomuchgaming commented 4 years ago

Same error, posting 1 stack of 8 dark iron bars (22 in my bags).

waytoomuchgaming commented 4 years ago

Same error, with Skullsplitter Coin, posting a stack of 15 (260 in my bag).

Again, as they stack by 250, aux had to grab from 2 different piles, which very likely seem to be part of the problem.

waytoomuchgaming commented 4 years ago

Same error, with Hakkari Coin, posting a stack of 15 (265 in my bag).

So, that invalidate my previous theory, because there was no reason to grab from 2 different piles there.

shirsig commented 4 years ago

Could you try manually deleting the addon and redownloading? And perhaps also the savedvariables. It's really strange that this happens to you so frequently and not once to me. Also, in classic, unlike vanilla, assembling the right stack sizes and posting multiple stacks is actually done with an api function.

waytoomuchgaming commented 4 years ago

OMG, i did it without thinking... and i lost all my saved searches. Hundred of them T_T And all my other settings (including the "hidden" one i can't find back, to see/set the starting price below competition). You really need to make an export settings thing.

No more errors since the deletion of saved variables... so far (i have not go under all my usual buy and sale, for obvious reasons).

shirsig commented 4 years ago

Damn, sorry :( The setting you're looking for is /aux post bid

waytoomuchgaming commented 4 years ago

After a fresh install of Aux: same error, posting 1 mithril casing (11 in my bag).

waytoomuchgaming commented 4 years ago

Same error, posting 1 stack of 8 dark iron bars (26 in my bags).

shirsig commented 4 years ago

Did you try disabling other addons? (I assume some others were updated around the same time for the client version?)

waytoomuchgaming commented 4 years ago

I kinda gave up on that one : even if it's a very common error, i just have to select another item, and the problem is gone (until the next time ^^). A bit annoying, but not game breaking. But today i got errors with dark iron bars, only when i post a stack of 8. I tried a lot of other kind of stacks of dark iron bars, but it's only the stacks of 8 that make the bug appear. It can still be (un)luck, tho.

shirsig commented 4 years ago

Did you ever try disabling other addons? I use it daily and still have never had this error.

waytoomuchgaming commented 4 years ago

No. I'm using around 50 addons, and finding the one (if any) causing the conflict will take forever. As it's a minor problem, i'll just live with it.

But i'll try again with only Aux next time i'm selling dark iron bars. As the stack of 8 causing the bug seem 100% reliable, these days.

waytoomuchgaming commented 3 years ago

And so, after some other inconclusive tests (no 100% reproducible, even if sometimes very close), i read "Updated how the Auction House is scanned. It will only scan now when a user places an item up for sale or they are viewing their auctioned item list. Added protections to the Auction House scanning to prevent it from interfering with any other addons or regular Auction House actions. This means that auction scans will only occur if C_AuctionHouse.IsThrottledMessageSystemReady() returns true and the server is ready for a query." from the BagSync changelog addon, and since that update, the error is gone.

So, i guess it was a conflict, after all, and i have an addon using the AH beside Aux, which i did not know.