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

Make sure that no string is emitted as an error #789

Merged
merged 1 commit into from Jul 20, 2016

Conversation

lpinca
Copy link
Member

@lpinca lpinca commented Jul 20, 2016

This patch makes sure that the error listener of the WebSocket object always receives an error. All errors now have a meaningful stack trace.

@@ -310,18 +312,9 @@ class Receiver {
* @api private
*/

error (reason, protocolErrorCode) {
if (this.dead) return;
Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This was added here 913afa3#diff-ee39beab4c8223a58e34e180ba59f345 but the issue it attempted to fix (#680) was actually caused by reentrance after cleanup.
This is no longer the case in master so it has been removed.

@3rd-Eden
Copy link
Member

Thanks for your contribution <3

@3rd-Eden 3rd-Eden merged commit 4167e5c into websockets:master Jul 20, 2016
@lpinca lpinca deleted the emit/errors branch July 21, 2016 05:43
@lpinca lpinca mentioned this pull request Dec 12, 2016
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.

None yet

2 participants