Stream state change for a non-existing channel

[matarife123]

errors do not interrupt mining

[DevilXD]

Hello o/

This should be more of like a warning level instead. This "error" comes from the websocket receiving a channel state update, for a channel that doesn't exist in memory at the time. This usually indicates problems with websocket properly managing the topics the main loop gives it. I suspect there might be a race condition at play here, since I've never implemented proper request-response to the websocket system twitch uses, simply because it appeared to work without that.

The good news is that, well, in this case you receive too many updates, because these channels aren't tracked anymore. The bad news is that, IIRC, the main loop's design won't "fix" this by reloading, and you'll actually need to restart the application to get rid of those.

As a TODO for myself, it'd be adding proper request-response system to the topic subs and unsubs logic of the websocket. I'll try giving it a shot again and see what I can come up with.

[DevilXD]

@matarife123 This has nothing to do with the topic of this issue.

If the autostart doesn't work for whatever reason, unchecking it and then checking it again should fix it. The autostart feature isn't smart enough to figure out that you've moved the folder elsewhere after enabling it. If that won't help (and there's a 99.9999999% chance it will), then please open a separate issue instead of commenting under a completely different one.