Skip to content
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

Error debuglog #1140

Closed
spunkerms opened this issue Jul 1, 2022 · 15 comments
Closed

Error debuglog #1140

spunkerms opened this issue Jul 1, 2022 · 15 comments
Labels

Comments

@spunkerms
Copy link

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

Please, help me with this issue ?

@thailyn
Copy link
Contributor

thailyn commented Jul 2, 2022

Hey, thanks for the report. Please include your DebugInfo.log file, so we can see what the issue is.

@mikenik4
Copy link

mikenik4 commented Jul 2, 2022

Looks like I have the same problem and it also started happening only recently, maybe my log with error will be helpful
DebugInfo.log

@CoutoSH
Copy link

CoutoSH commented Jul 4, 2022

DebugInfo.log

same is happening to me, here more data if u guys need.

@PabloAlarco
Copy link

I have this same issue happening since several days ago. Any news about it?

@PaloCerezo95
Copy link

PaloCerezo95 commented Aug 22, 2022

same problem

DebugInfo.log

@GunsnrosesHG
Copy link

DebugInfo.log
same here

@GunsnrosesHG
Copy link

I have this same issue happening since several days ago. Any news about it?

did you find a solution ?

@chrlsfrmg
Copy link

managed to solve?

@GunsnrosesHG
Copy link

GunsnrosesHG commented Dec 22, 2022 via email

@thailyn
Copy link
Contributor

thailyn commented Dec 22, 2022

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.

Omga4000 added a commit to Omga4000/Procurement that referenced this issue Dec 22, 2022
Omga4000 added a commit to Omga4000/Procurement that referenced this issue Dec 22, 2022
Omga4000 added a commit to Omga4000/Procurement that referenced this issue Dec 22, 2022
@Omga4000
Copy link

Omga4000 commented Dec 22, 2022

@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:
Omga4000@d8c2e2f
Omga4000@98f6c7e
Omga4000@fefd751

Let me know if that works for you.

@thailyn
Copy link
Contributor

thailyn commented Dec 22, 2022

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.

@thailyn thailyn added the bug label Dec 22, 2022
@CoutoSH
Copy link

CoutoSH commented Apr 14, 2023

DebugInfo.log
same error, crucible league

@thailyn
Copy link
Contributor

thailyn commented Apr 14, 2023

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.

@CoutoSH
Copy link

CoutoSH commented Apr 19, 2023

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

@thailyn thailyn closed this as completed Dec 6, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

9 participants