Chillymosh

The cause of this is possibly due to an = in the message content of a subscription message or other USERNOTICE message.

It will continue running

We were waiting for the merge of the and refactoring of the IRC parser before addressing this. We will look further into it soon.

@Commaster `tags = dict(x.split("=", 1) for x in rawData.split(";"))` will most likely work if you would like to test locally on 2.4.0 install direct from git ``` python -m pip...

@Commaster 2.4.0 is now available on pypi. We have updated the join_channels logic in this version, although not sure how #209 is relevant to this issue. Try updating to 2.4.0...

This may have already been resolved in one of the recent versions or master. Network timeouts to the websocket are a totally different thing and have their own errors raised.

1. How many channels are you joining in your `initial_channels`? 2. Are you joining any channels manually after `event_ready` using `join_channels()` if so then how many channels are there in...

Event_ready now fires in 2.4 with empty initial_channels, as per the changelog, although this issue is isolated to calling join_channels manually.

Which version did you start getting this error on? If it's master after which commit did you last install?

@preeded I believe I have resolved this in f111e676cbd2988ca8d99ba84b0b8be118354ae1 which you can test by installing TwitchIO direct from master