-
Notifications
You must be signed in to change notification settings - Fork 3
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
After tabs are loaded, most unselected and selected a few the shop does not update and errors out. #26
Comments
@leet0rz I think you are the first person to report this error. I have not seen it either, so it would probably still happen using the v0.10.3 alpha releases. The ERROR message you copied suggests that there was a problem refreshing the selected tabs--the 404 error is concerning, and I can't think of how that might be happening. This may be causing the shop update code to fail; I'm not sure yet, so I'd like to troubleshoot that before looking into the shop update issue. It looks like you have copied output from the GUI's event log. This just contains some of the logging information. There's more in the log file, which is probably in a file like this (on Windows):
Can you find the section of that log related to the ERROR message you copied? There is probably additional logging information about what happened. If you can find it, please copy those lines here. In case there you cannot, I can also walk you through how to run acquisition with more detailed logging. |
It seems its not refreshing again, I was clicking the wrong option it seems to be sent to the forum through "update shop thread". I am not sure but I think whenever I restart the program it will refresh the tabs and collect the right snapshot but not when I try to refresh manually, then I can proceed to update shop thread and it will correctly. Are you still interested in a log or no? |
Yes, if you would like me to troubleshoot your issue I need more detail, because the manual refresh is working for me when I test it with my account and a few tabs. If you decide to post the log, it would be useful if you first delete the log file, then run acquisition and experience the problem. This will keep the file size down. However, please note that the log file may contain your character and account names. |
Maybe this is what you are looking for? I just ran my sequence of actions and copied the latest information from the log. Seems to be similar to what I saw in the console in "Event log". |
@leet0rz Thank you, that helps narrow it down. With that 404 error, I'd like to see what shows up in the log file if you turn up the logging level. If you can try the most recent alpha, it makes it easy to set the level of logging detail from the UI: That will help me pinpoint if the issue is happening during the tab refresh, or during the shop thread update. |
Is this correct?:
[EDIT: I have edited the personal details and limited the log to just the parts relevant to this bug. --@gerwaric] |
Yes, that was perfect. The error was because you had a character with "๏" in the character name. That is a non-ASCII character, and acquisition was not handling it correctly. This should fix it: https://github.com/gerwaric/acquisition/releases/tag/v0.10.4-alpha.4 Let me know if that works for you. |
Ah yeah, I did a file search and replace on my username and account name. I see what it is now tho, its that circle symbol that a lot of people use in their names that is messing it up. Good to know and thankfully if we would like we can just change names now whenever we want. I will try that version in a bit and report back. |
You should be able to use those special characters now. I'm surprised no one has reported this bug yet, because it looks like it's from an old part of the code. |
Thanks, seems to be a bit different now. Keep getting one of the errors and some other stuff up above:
This "Failed to find item" will also happen with just 1 rogue coin or anything else in the tab. Ideas? |
Those warnings about being unable to categorize those items are new.. previously things were just being silently ignored. So now at least I can try to look into it. The shop thread errors could be due to the fact that acquisition apparently doesn't know rogue markers are a currency item. I'm not sure about this, so I'll dig into that as well. There are also some small UI improvements and bugfixes coming in the next alpha. |
I just tested without and that seems to be the case lol, replaced them with id scrolls and now it works. |
Good find. I'll setup a stab in standard with all the stackable currencies to see which others are missing. Do you have a few mirrors of Kalandra I could borrow? For "testing" ;-) |
Cool. I do not unfortunately, hehe. |
I get a similar problem |
@PyroCalzone Thanks for reporting that error. Does it happen every time you start acquisition and do two manual refreshes? |
Started happening for me as well just recently, in manual refresh yeah. After that it will get stuck on:
|
@leet0rz @PyroCalzone what versions are you each using? Let me know and I'll see if I can replicate the problem. |
0.10.4-alpha.4 Would also like to include these warnings I get on startup each time:
|
@leet0rz thanks for including those warnings. Acquisition uses files from https://github.com/lvlvllvlvllvlvl/RePoE to automatically categorize items, and the warnings you're seeing are from items that aren't included in the RePoE data. I added those log messages as warning, but they are probably not worth showing by default. I'll downgrade them to INFO messages in the next beta. That will prevent them from cluttering the UI, but they will still be available in the log if someone wants to turn up the logging level. |
@leet0rz @PyroCalzone I haven't been able to replicate this issue on my own yet. Could each of you try https://github.com/gerwaric/acquisition/releases/tag/v0.10.5-alpha.2 and let me know how it goes. If you still get the 404 error, the next step would be to take a look at more detailed logs. I can walk you through that process here or on discord if necessary. |
Still getting these, and its weird when launching the application it says 0.10.4-alpha.5, I entirely removed it and installed it again but the version name remains that and not 0.10.5-alpha.2 Maybe you forgot to update and have it say what version it currently is? I dont know. Icon also went away for some reason: |
@leet0rz thanks for the prompt feedback as always. The version and app icon issue are probably because I swapped the build system. However, I can't troubleshoot that yet because microsoft anti-virus isn't even letting me run the installer now. I ran into this issue last year, but I forget how I solved it, so I may lose some time trying to fix that. In the meantime, if you can turn up the logging to TRACE via the settings menu, it might show more information about the 404 problem. Specifically it would be nice to see what url it's requesting. I suspect there's a bug in the url generation, since that 404 error indicates it's trying to request a invalid |
@leet0rz ok, I got the virus warning solved, and I have replicated what you've seen with versions. I'm tackling that next. |
No worries 👍 There are a few videos on youtube showing how to disable windows defender if that is the one you are referring to, should be through "edit group policy" somewhere I believe. Logs, changed the acc/user names and removed some of that:
|
@leet0rz I have a new alpha release for you: https://github.com/gerwaric/acquisition/releases/tag/v0.10.5-alpha.3. This one fixes the version issue. It was a bug in the installer script that caused an old version of the executable to be bundled into the installer. The way acquisition checks for updates has also changed, so you'll see more information about available updates. (It will also always show you the optional update dialog box at startup when you are running a pre-release version like one of the alphas). For the 404 error, do any of your characters have any non-ascii characters or symbols in their names? Does your account name have anything like that? |
I did have a weird character yeah, I changed the name now. My account name just has regular letters.I have different errors now it seems:
Do you want me to do a full log on this as well or is this fine ? |
Sorry for the wait, I've downloaded the version you linked earlier (0.10.5-alpha.3). I was also experiencing the issue that leet0rz was, with the I also have a character named in Chinese text. Though there is nothing wrong with the character's name wherever it's displayed.
|
@leet0rz @PyroCalzone Thanks. I'm finally able to replicate the 404 error myself. I thought I had fixed the unicode issue, but obviously not. I'll post to this thread when I have it fixed. |
That's fine for now, because I can replicate some of these issues myself. I'll let you know when I have an update or need more information. |
I've been testing acquisition with a character with unicode ( Also, the |
I was wrong. This wasn't a unicode issue. What was happening is that when a user was only refreshing characters, acquisition was generating a request for an invalid stash tab. This caused the 404 error. Here's an update that should fix it: https://github.com/gerwaric/acquisition/releases/tag/v0.10.5-alpha.4 EDIT - Please hold off using alpha 4. It's causing the occasionally rate limit violation I'm debugging now. |
Seems to be working now, thanks for the fix! Hope we were of some sort of help lol. |
I always update manually when i put items in and so on, I should be good on the rate limit violation. |
There's a new release that should fix these errors and avoid rate limit violations better: https://github.com/gerwaric/acquisition/releases/tag/v0.10.5-alpha.5 If you can try it out, please let me know if anything is broken. I'm trying to get acquisition ready for the transition from POESESSID to OAuth. |
Getting the following error after tabs has been loaded in. What I am doing is unchecking everything, checking those tabs of interest and trying to refresh those to the store at the forum. It does not seem to send any items to the store, it just gets stuck with the following messages:
I am currently on the latest stable 0.10.2 and not any of the alpha ones. Is there a fix for this or should I go over to the alpha ones to fix this, what is the most usable version currently?
Error:
The text was updated successfully, but these errors were encountered: