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

Fixes #235 type error where channel does not exist #236

Merged
merged 1 commit into from
May 29, 2014

Conversation

qq99
Copy link
Contributor

@qq99 qq99 commented May 25, 2014

Fixes #235

Not sure if it's even a good fix, but I found it necessary to have at least this much, otherwise it'd just explode and kill my proxy server (I couldn't wrap it in try either)

@qq99
Copy link
Contributor Author

qq99 commented May 25, 2014

The package.json changes were updated by npm init and me spamming enter, seems to be the new default format / should be a noop

@katanacrimson
Copy link
Contributor

package.json changes seem to be indentation, and thus not something that should be changed in a PR. I'd suggest dumping that commit and then using only one commit for your change overall.

@qq99
Copy link
Contributor Author

qq99 commented May 26, 2014

will do

@qq99
Copy link
Contributor Author

qq99 commented May 26, 2014

Fixed!

osslate pushed a commit that referenced this pull request May 29, 2014
Fixes #235 type error where channel does not exist
@osslate osslate merged commit 61105b8 into martynsmith:master May 29, 2014
@qq99
Copy link
Contributor Author

qq99 commented May 29, 2014

I'm still a bit curious as to how this happens, but I didn't have time to really dig into the code fully to understand why, might be a latent bug?

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

Successfully merging this pull request may close these issues.

Sending nick out of sequence can cause exceptions
3 participants