TwitchDropsMiner-updated: Application Terminated "GQL error: [{'message': 'service error', 'path': ['claimDropRewards']}]" (version fa75358)

04:33:37: Fatal error encountered:
04:33:37: 
04:33:37: Traceback (most recent call last):
04:33:37:   File "main.py", line 158, in main
04:33:37:   File "twitch.py", line 769, in run
04:33:37:   File "twitch.py", line 825, in _run
04:33:37:   File "inventory.py", line 232, in claim
04:33:37:   File "inventory.py", line 138, in claim
04:33:37:   File "inventory.py", line 154, in _claim
04:33:37:   File "twitch.py", line 1573, in gql_request
04:33:37: exceptions.MinerException: GQL error: [{'message': 'service error', 'path': ['claimDropRewards']}]
04:33:37: 
04:33:37: Exiting...
04:33:37: 
04:33:37: Application Terminated.
04:33:37: Close the window to exit the application.

Reporting just in case.

About this issue

  • Original URL
  • State: open
  • Created 2 years ago
  • Reactions: 1
  • Comments: 36 (14 by maintainers)

Most upvoted comments

@rothexD ohhhh, maybe this whole thing is just #63? Can anyone deny this?

Right now, I’m haveing the Issue on Smite. There are 2 campains, one of them I finished though.

22:36:32: Fatal error encountered:
22:36:32: 
22:36:32: Traceback (most recent call last):
22:36:32:   File "main.py", line 160, in main
22:36:32:   File "twitch.py", line 772, in run
22:36:32:   File "twitch.py", line 828, in _run
22:36:32:   File "inventory.py", line 232, in claim
22:36:32:   File "inventory.py", line 138, in claim
22:36:32:   File "inventory.py", line 154, in _claim
22:36:32:   File "twitch.py", line 1575, in gql_request
22:36:32: exceptions.MinerException: GQL error: [{'message': 'service error', 'path': ['claimDropRewards']}]
22:36:32: 
22:36:32: Beenden...
22:36:32: 
22:36:32: Anwendung gestoppt.

image

my app crashed with the latest release, error looks the same, the campaign had 2 drops, 1 drop with half the time remaining the other drop was finished and successfully claimed

@rothexD Can you give more detail with full logs (-vvv --debug-gql --debug-ws --log)? The game might also be helpful, but probably not, because someone mentioned Overwatch 2 here, which I mine anyway, and have had no crash.

I’m not entirely sure why was I summoned here. In case you weren’t aware, a “service error” means exactly what it says - Twitch service is having an internal error that it cannot immediately resolve. Retrying a particular GQL request in that instance can either give you the same error over and over ad infinitum, or generally means that something in the Twitch service that was working so far, has temporarily stopped working, and the request cannot be correctly processed at this time. ETA on resolving issues like this usually ranges from a few minutes, to “never”, if the miner happens to hit a particular path that no standard client will ever hit (which happened in https://github.com/DevilXD/TwitchDropsMiner/issues/347).

Since both of these cases generally mean that the standard retry loop of “try again 1/2/4/8/16/etc. seconds later” is a terrible idea, the handling of that particular error by the standard retry loop is commented out. Instead, a more appropriate, longer retry loop is planned to be implemented by https://github.com/DevilXD/TwitchDropsMiner/issues/417, as a part of the v16 release task list at https://github.com/DevilXD/TwitchDropsMiner/issues/234.

More info can be found under the issues I’ve linked. Other that that, this is still an open thing to take care of “at some point”. If it happens occasionally, but otherwise everything works, it’s a temporary issue and you should just wait, and retry with the miner at a later time. If it happens reliably and every time, it’s probably worth reporting, just like https://github.com/DevilXD/TwitchDropsMiner/issues/347 happened to be related to trying to claim an outdated drop. You can report these on the original repo.

PS: If you’re in dev and you’re getting this semi-often, and you really, really want to just not let these stop your dev work, plus you’re confident you aren’t hitting a bad request path, you can uncomment that line. However, using this in the long run (and also pushing it to prod) is a bad idea, as spamming clearly non-working requests can quickly alert Twitch that something fishy is going on. By pure dev logic, all service errors are most likely logged somewhere, and Twitch is continuously working on resolving these and improving their service. If they find out a miner spamming bad requests, they’re gonna take more steps to block the project yet again. The miner is supposed to mimic a diligent Twitch user and thus keep requests at minimum, not brute-force it’s way to the drops by spamming Twitch with requests. Keep that in mind.