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.

Sign up for GitHub

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

Jump to bottom

Socket error is escalated twice to a connection callback. #17

Closed

kadishmal opened this issue Jan 30, 2015 · 1 comment

Labels

bug

Milestone

Contributor

kadishmal commented Jan 30, 2015

Migrated from http://jira.cubrid.org/browse/APIS-691.

Due to a bug in Node.js (as of 0.10.15), the socket error is escalated twice.
Any socket error should be handled only once and not by the connection callback but the callback which triggered the socket activity.

kadishmal added the bug label

kadishmal added this to the 2.1.1 milestone

Contributor Author

kadishmal commented Jan 30, 2015

Fixed in v2.1.1 release.

kadishmal closed this as completed

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment