Closed spunkerms closed 7 months ago
Hey, thanks for the report. Please include your DebugInfo.log file, so we can see what the issue is.
Looks like I have the same problem and it also started happening only recently, maybe my log with error will be helpful DebugInfo.log
same is happening to me, here more data if u guys need.
I have this same issue happening since several days ago. Any news about it?
same problem
DebugInfo.log
DebugInfo.log same here
I have this same issue happening since several days ago. Any news about it?
did you find a solution ?
managed to solve?
Hey no i didn't
On Thu, Dec 22, 2022, 6:38 AM chrlsfrmg @.***> wrote:
managed to solve?
— Reply to this email directly, view it on GitHub https://github.com/Procurement-PoE/Procurement/issues/1140#issuecomment-1362440631, or unsubscribe https://github.com/notifications/unsubscribe-auth/A2WY3XZCSLAXFAQDG2NA47DWOPSOBANCNFSM52LLV2LA . You are receiving this because you commented.Message ID: @.***>
My apologies for not following up for a while. To confirm, this is not working in the 1.29.1 version, as well? I'll take a closer look ASAP.
@thailyn @GunsnrosesHG @chrlsfrmg I didn't think there's still demand for the program - nice to see people are still interested.
I've cloned this repository and (temporarily) fixed the issue. I'll create a better fix in the near future. Feel free to download the latest release I've created from my own repository, it should be public. https://github.com/Omga4000/Procurement/releases/
You can also see my commits if you're worried about any funky business: https://github.com/Omga4000/Procurement/commit/d8c2e2f0a7fc68c6a62dc407082b970ef8f9d925 https://github.com/Omga4000/Procurement/commit/98f6c7e35b6c0928ce39bbe1cd31a5bfd1b8c607 https://github.com/Omga4000/Procurement/commit/fefd7518e2e63e5a650407c27a4488ece8db9fa9
Let me know if that works for you.
I have a pre-release of Procurement version 1.29.2 available here. Please try it out and let me know if the login issues are resolved.
DebugInfo.log same error, crucible league
Hi, @CoutoSH , thanks for the report. Your error is different. In your case, Procurement is trying to send too many requests (beyond what GGG allows per minute). This shouldn't happen when using Procurement alone, but things can get complicated. What were you doing in Procurement when you got the error?
Are you getting the same error each time you run Procurement? Please wait at least 2 minutes since you got your last error before trying with a new instance of Procurement.
Are you using other apps at the same time which use GGG's API? Procurement only tracks its own usage, so it will not always smoothly handle having a lower quota than expected.
Hi, @CoutoSH , thanks for the report. Your error is different. In your case, Procurement is trying to send too many requests (beyond what GGG allows per minute). This shouldn't happen when using Procurement alone, but things can get complicated. What were you doing in Procurement when you got the error?
Are you getting the same error each time you run Procurement? Please wait at least 2 minutes since you got your last error before trying with a new instance of Procurement.
Are you using other apps at the same time which use GGG's API? Procurement only tracks its own usage, so it will not always smoothly handle having a lower quota than expected.
Sorry for taking so long to reply...
it worked, I think that the problem was me and my brother trying to do stuff at the same time. the API doesn't like when we do searches and use it at the same time.
thx, and its working fine, my bad
Error downloading account name, details logged to DebugInfo.log. Please open a ticket at https://github.com/Stickymaddness/Procurement/issues and include your DebugInfo.log![imagem_2022-07-01_005433104](https://user-images.githubusercontent.com/108506320/176820255-f79ab448-adb7-4e35-9ec6-db3e2cb1a8d7.png)
Please, help me with this issue ?