Unless you were watching something else on Twitch in the meantime - the miner will actually receive those events as well. No watch events being sent would mean no points events being received. This is also an indication of the watch events still being sent properly, as each event yields +10 points every minute, and +50 claimable points are yielded every ~15 minutes. If no watch events would be sent, the timer would stop counting down and get stuck at the closest whole minute.īut still claiming channel points as it seems If the watch event is sent, but there's no drop progress response within 10 seconds afterwards it's the watch loop's job to "manually" trigger a minute countdown, so that the timer continues to tick down even when the bug occurs. There's a lot of confusing information here.Īre you sure of that though? Twitch has a bug with displaying progress of some drops, where it'll "appear stuck" (no drop progress updates are received) but actually count properly in the background, and then automatically get unstuck at some point later on. Guess the token got invalidated? Had to remove the cookies.jar and login again. No matter how many times I try to log in, the result is the same, finally I restored the previous cookies and it actually works again (so I still don't understand why my account can't log in in the software, but I can use it now)įile "asyncio\base_events.py", line 616, in run_until_completeįile "twitch.py", line 1059, in gql_requestĮxceptions.MinerException: GQL error: Ĭannot connect to Twitch, retrying in 1 seconds. Then I downloaded the latest version, because the old version will report an error, I was afraid that Twitch judged my account as a robot, so I deleted the previous cookies and tried to log in again, but I encountered this error, no matter what Later, I went to Github and looked at it, only to find that 2 big version updates have been made recently. I used it for a long time, but it kept getting an error some time ago, but I didn't have time to worry about it. I used the old V12 version at the beginning. However, I solved it now, the process goes like this: I looked, but I think it's different from what I encountered, and my error is exactly the same as this one.
This is a continuation of the story, really.
Please, if you're new to the issue, see #40 for more information. Using a browser cookie will cause points and drop claiming to error out.
0 kommentar(er)
