Skip to content
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

Client.part(channel) doesn't always cause client to leave the channel #212

Open
azazael13 opened this issue Mar 8, 2017 · 3 comments
Open
Milestone

Comments

@azazael13
Copy link

Actual behaviour:
I have a hard time reproducing this error, but on occasion I will issue a client.part and my bot will not leave the channel. It will however remove the reference from client.getChannels(). When I try to rejoin the channel via client.join the client is unable to join because it already exists and instead continually spams the join command.

Expected behaviour:
When I do a client.part the client should leave the channel and remove the channel from the list.

Error log:

Insert your error log here

Server configuration

  • Operating system:
  • Node version (if applicable): 4.5.0
  • NPM version (if applicable): 2.15.9
  • tmi.js version: 1.1.2
@stachu540
Copy link

stachu540 commented Mar 8, 2017

Your resolve for issue: #204.

@azazael13
Copy link
Author

@stachu540 That isn't a resolution for the bug, that is a workaround.

@stachu540
Copy link

There is no point to fixing it. All things works on Websocket environment (expected API). Expectation bugs near Server-Side, not on Client. There is nothing they can do.

@Schmoopiie Schmoopiie added this to the 2.0.0 milestone Apr 15, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants