-
-
Notifications
You must be signed in to change notification settings - Fork 175
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
MinerException: GQL error: [{'message': 'service error', 'path': ['channel', 'viewerDropCampaigns']}] #435
Comments
I've been getting this too for about 3 days now. The issues you linked aren't related but these are:
Update: mine just started working again within the last hour 🎉 Another edit: if you find this, try turning on "priority only" and messing with the games in that list. it might be associated with only one of those games. |
Correct, there isn't anything that can be done on your side, as "service error" is just the Twitch website crashing and generally having internal issues. On my side, handling this in a better way is tracked by #417. I feel there's a need to create a better logging system, because this issue is caused by a single channel, and there might be something specific about it that's causing the crash, just like what happened with the drop claiming time limit: #347 (comment) |
Thank you for your replies! My client works again, as Twitch's side has been fixed, I guess. |
@DevilXD I was playing around with my priority list and does seem like it's linked to either a single channel or single game. Got any ideas for an easy way to figure out which channel/game is causing this? I rather just remove it for now so i can at least mine other drops instead of this killing the entire service. |
Try it with this latest commit: a536dde |
Doesn't seem to work. The error for this I changed it to try:
available_drops: JsonType = await self._twitch.gql_request(
GQL_OPERATIONS["AvailableDrops"].with_variables({"channelID": str(self.id)})
)
except MinerException as exc:
logger.info("Channel caused an error. Skipping channel: {self._login}")
return None and it threw out I have my fix in place for now so everything is great again. |
I still encounter the error despite this commit.
Maybe you could suggest the fix as a pull request. Edit: I did it for a try in: I will tell you if I encounter the error again with this commit. |
@woctezuma The commit was never supposed to resolve any issues, only add context information. This isn't a fix by any means.
@jaredkotoff That's my bad. The exception handler was added in the place where a "service error" did occur in the past, but it was actually a couple lines lower that was crashing in your case. This place can actually salvage the crash, because the stream information exists already, and just the "drops_enabled" flag is updated when necessary. Please try this latest one: 5dea41a |
Starting today, I have encountered a fatal error.
Maybe related:
The text was updated successfully, but these errors were encountered: