-
-
Notifications
You must be signed in to change notification settings - Fork 173
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
GQL "service error" #347
Comments
Came to report the exact same issue. I think the app keeps some cache data somewhere, I'll try clearing that too. |
Twitch Drops were simply down. Restart your bots, and it should work again. |
Could it be feasable to add a catch for whenever this occurs? ANd then a retry timer in like... say every 5 minutes? EDIT: |
Hello. "Service error" means the service is temporarily down, and there isn't much I can do about it. Handling such an error isn't as simple as retrying the request, as downtimes usually last longer than mere seconds, or even minutes. The miner's internal logic isn't prepared to just "go idle" and recheck every so often. Such a functionality would require a dynamic timeouts system, instead of the current static one. This seems as one of the things that #220 should take care of, but that puts it into a far future. For now, the solution is to just verify the drops system is available again, and then restart the miner manually. |
@epsgerry02 I think you've misunderstood. The error means that the Twitch website itself is having server issues, and there's nothing you can do on your side to help it, other than waiting and checking https://www.twitch.tv/drops/inventory every so often, to see if the list of drops you've claimed loads again. If it does, and does so reliably (don't rely on the page loading correctly only once, refresh 2-3 times to be sure), then restarting the miner will "fix" the issue. Restarting it before that won't help. |
on start app |
same error |
The bug is still prevalent btw 11:57:42: Fatal error encountered: |
work now for me :S |
Doesn't work for me... |
Just as a note here, this will keep happening, until there are steps taken to mitigate it. There's no value in having this reported 5 times to me, if the reason is already know, and a fix idea already planned. The only thing that'd help me now, is having enough time to sit down to this properly, which I don't have now. For now, as mentioned higher up here, use these as mitigation steps: #347 (comment) |
I was able to reproduce this issue on my end. Based on the findings, it seems to be caused not only by server instabilities, but also by a new directive from here: https://help.twitch.tv/s/article/mission-based-drops?language=en_US#claiming
21ad099 attempts to take this information into account, so you should see less "service error" crashes in the latest development build. |
Since no more reports are present, I think I can close this one now. |
Version: d780445
Error:
21:04:30: Fatal error encountered:
21:04:30:
21:04:30: Traceback (most recent call last):
21:04:30: File "main.py", line 158, in main
21:04:30: File "twitch.py", line 764, in run
21:04:30: File "twitch.py", line 806, in _run
21:04:30: File "twitch.py", line 1599, in fetch_inventory
21:04:30: File "twitch.py", line 1548, in gql_request
21:04:30: exceptions.MinerException: GQL error: [{'message': 'service error', 'path': ['currentUser', 'inventory', 'gameEventDrops']}, {'message': 'service error', 'path': ['currentUser', 'inventory', 'dropCampaignsInProgress']}]
21:04:30:
21:04:30: Exiting...
21:04:31:
21:04:31: Application Terminated.
21:04:31: Close the window to exit the application.
Note:
Happens now on every start , cleared the folder and re extracted the app but getting still the error.
The text was updated successfully, but these errors were encountered: