Open axi92 opened 1 month ago
DevilXD
commented
1 month ago I sort of knew that this may just come back at some point.
Have you done any scrubbing of the log file yourself? Like, did you delete any parts of the log before posting here? I'm asking because some data is missing, mostly some variable contents.
axi92
commented
1 month ago Yes I tried to get rid of some tokens and hashes. I don't know if they can be traced back to the account used there. Would be nice to have a guideline on how to post logs not exposing sensitive data.
DevilXD
commented
1 month ago The guideline is simple - don't post DEBUG logs, at all. Doing so exposes too much information, and even though it is helpful to narrowing down the cause, debug logs contain raw requests data, which often contain information that's used to authorize your account to twitch (the authorization token). This is true for both GQL and Websocket. Websocket straight up sends the auth token in the body itself, so that's logged for sure. GQL may log the auth token if the headers are included in the log,
I've actually wanted to remove the logging system entirely out of the application for this very reason, as I myself don't really use anything besides the CALL logging level for dev work, and normal level otherwise. I use the VSCode debugger to determine what the application is doing, not relying on the logging messages at all. They're still there mostly for historical reasons.
Btw, it's too late, and you've already exposed your authorization token in that log above. My recommendation would be for you to change your Twitch account password as soon as you can, to invalidate the token.
axi92
commented
1 month ago At least I cleaned-up all my twitch connected apps with that :+1:
Is there anything I can run to help debug that issue?
DevilXD
commented
1 month ago Not really, no. The debug log you've posted is sufficient for now.
The log implies that the last operation the miner was doing, was deleting an on-site notification. The miner uses a hook to the notifications system, to deduce when a drop becomes available for claiming, and triggers a reload when a "new drop" notification is received. The reload process then claims the drop. For convenience sake, the miner also deletes/dismises the drop claim notification, so that the user doesn't have to bother with clearing lots of notifications from already-mined past drops every so often, The last GQL operation logged points at such deletion process happening.
There's no messages printed from the reload process, so I don't know if it's the notification handler that caused the issue, or the reload process itself. For now, this issue is stuck in some kind of a limbo, and it'll remain there until someone finds the cause and can reliably repro it.
Hi again, my ui is again in the same state. As in this issue https://github.com/DevilXD/TwitchDropsMiner/issues/548 Run from source. commit: d333c86598ba00871a1b24a3b93d2c5954dd93a2 Here are the logs:
I have it run now with the latest commit 66c361103fc2d8c0a93ef875976c7fb4244968d5