-
Notifications
You must be signed in to change notification settings - Fork 100
Acquisition forgot all my prices again... #381
Comments
Sorry to hear. This is unfortunately not easy to debug as there are so many variables involved and to fix/test we would need to reproduce somehow. The more details you can give regarding the conditions under which this happened the more likely it will get some attention. Also, have you tried totally resetting your database as desribed in [Troubleshooting First Steps] and has the problem occured since? |
Specifically, did you see a condition on which you're tabs where fetched and they showed no items in them? That would cause all pricing data for the tab to be removed. |
No, all the items return but with no pricing. It's as if I take them out, refresh tabs, then put them back in =/. Honestly it is driving me crazy and every time it happens it takes literally hours to reprice everything. |
It seems to happen whenever people are reporting lag spikes or server issues. I'm guessing it has to do with the Trade API somehow telling Acquisition that my tabs are "empty". |
There must be some way to back up the data to restore prices or to uniquely identify items? |
Why would the data get removed? We should never remove buyouts, and I'm sure it used to work like this before.
… On 27 Dec 2016, at 03:50, ericsium ***@***.***> wrote:
Specifically, did you see a condition on which you're tabs where fetched and they showed no items in them? That would cause all pricing data for the tab to be removed.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.
|
I added compression of buyouts a long time ago thinking there could be some strange side effects if we leave stale pricing data around which can suddenly be applied unexpectedly to future items. I think the problem is that some new error conditions related to 2.5.0 now allow us to get to the compression code somehow. See 'CompressItemBuyouts' and 'CompressTabBuyouts' in buyoutmanager. One option is to simply skip the compression and live with forever growing database. Other option is to figure out why we're not catching error conditions properly and getting to the compression code. |
Looking into this a bit today, can you answer a few more questions:
|
While thinking about this issue and came up with #383. I think it's highly likely that that issue is what was causing your problem. |
Please, I will give you ownership of my soul if you guys fix this. Again with the lag spikes on US servers, all my stash tab prices were deleting and I have to spend several hours to reprice... I don't know if I can handle any more of this and still play this game.
The text was updated successfully, but these errors were encountered: