Application Terminated "GQL error: [{'message': 'service error', 'path': ['claimDropRewards']}]" (version fa75358) #86
Labels
Bug
Something isn't working
Help needed
General or specific issues that require some additional assistance to solve
Comments
|
Is this the same drop as #85? I don't know what I can do about it, because I don't have the issue. |
|
it's not. Not sure what was the drop that caused the issue but the ones I have scheduled right now are Overwatch 2, SMITE and Brawhalla. All, F2P. |
|
Same issue, right now it is watching Overwatch 2 channel ow_esports for the drops. Every time it claims the drop it crashes but the drop is claimed after a restart (don't know if before or after the restart). |
|
"service error" is explicitly commented out in error handling for whatever reason TwitchDropsMiner-updated/twitch.py Lines 1559 to 1578 in e00187f edit: happened in 5e862f9 with no explanation given. |
|
I will wait for @DevilXD to comment here or on the pull request before reverting something, that was clearly taken out on purpose. |
Windows200000
added
Feedback Wanted
|
It should happen 1 more time for me, so I'm going to log what happens. |
|
@Goth667 Thanks for your effort, but read #86 (comment) and #86 (comment) |
Yeah I did, just thought I post the log because the 2nd to last line is the error response and it might help Devil. Like maybe it's a new error that wasn't returned before or something. |
@Goth667 Well, you clearly did not |
|
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 DevilXD#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 DevilXD#417, as a part of the v16 release task list at DevilXD#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 DevilXD#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. |
|
At least from what I've been able to test (and replicate), this error seems to happen when TDM tries to auto-claim a drop that has already been claimed (e.g. by an extension like BetterTTV, that also auto-claim drops) |
|
Two things here:
|
|
Hi, I released v15.6.0, can I get a confirmation that this is still an issue? I'm always running the latest in-dev to try and find bugs before releasing and have never experienced this. |
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 ( |
|
The game
the game was PUBG, i did not continue with the second drop, but if it crashes again (remaining time is ~30 minutes) i will let you know |
|
the second drop was claimed without any issue |
|
I will try the PUBG campaign in debug mode then. |
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
|
@DarkViRnD your comment about the crash belongs here |
Windows200000
changed the title
|
I still have never gotten this error, mining all kinds of stuff. A full log with |
Like the one I posted before ... |
|
@Goth667 Where? You mentioned you were going to when I was waiting to hear from DevilXD, but I can't find it. |
I deleted it, because it wasn't needed. Here it is again: Logs |
|
@Goth667 This shows that the drop was actually done and was not claimed 5 seconds before. Is it possible, as DevilXD and JustaDaydreamWarrior suggested, that you have an extension claiming it? I have not had this issue with any drops. |
I do have an extension, but twitch isn't open in the browser. I disabled BetterTTV for now. Maybe they changed how they collect the drops. |
|
I simply can't work on it, until I figure out what causes the issue and can replicate it. Maybe @JustaDaydreamWarrior could do some more testing to figure out, whether this is indeed just BetterTTV, or happens even without the extension. |
|
I often get this error, I don't have any extensions. |
Even with the extension beeing turned off, it still crashes. |
|
@Windows200000 i have just had this issue with rust, i was watching a streamer that had a special drop and it was finishing the special drop but it tried to claim the non finished generic drop that all streamers have. Unfortunately because im a noob i dont have the logs |
This was referenced Jun 12, 2024
|
Have same error with last release from here. Game Halo Infinite |
|
Got the same error with every game I tried to mine. Last one was The Finals. First the OG one from DevilXD stops logging time so the drops progress and now this fork crashes every time it claims a drop. There either has to be something wrong in the OG code that didn't get fixed properly in this fork or Twitch managed to outsmart this program. 15:01:19: Fatal error encountered: |
Closed
|
I had the issue also it seems it was caused by the fact I had a browser extension that automatically claim drops. The extension was claiming drops just before the app and this seems to cause the issue on the app, I disabled the extension and now I no longer have the issue. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Reporting just in case.
The text was updated successfully, but these errors were encountered: