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 uncaught errors are correctly logged. Fixes #589. #591

Merged
merged 2 commits into from
Feb 7, 2017

Conversation

vqvu
Copy link
Collaborator

@vqvu vqvu commented Feb 7, 2017

We signify uncaught errors by doing this.emit('error'). This throws an
error if there are no bound handlers. Previously, for promise-based
streams, such thrown errors may propagate up to the promise and be
swallowed by whatever promise implementation the user is using.

We can push data asynchonously to fix this problem. While we're at it,
also return null from promise handlers so that bluebird doesn't
complain. See #588.

We signify uncaught errors by doing this.emit('error'). This throws an
error if there are no bound handlers. Previously, for promise-based
streams, such thrown errors may propagate up to the promise and be
swallowed by whatever promise implementation the user is using.

We can push data asynchonously to fix this problem. While we're at it,
also return null from promise handlers so that bluebird doesn't
complain. See caolan#588.
@vqvu vqvu merged commit 8393ad6 into caolan:2.x Feb 7, 2017
@vqvu vqvu deleted the throw-uncaught-errors branch February 7, 2017 06:09
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.

1 participant