catch processing errors and emit them as events #13
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Previously, if the server received a malformed packet, the request processing would throw an uncaught error which can end up killing the node process.
Instead, add a try ... catch handler around the Request / Response processing and trigger an error event which can be caught and handled gracefully. Include an error message, the actual Error object, and the connection info in the event callback so aid debugging and make it possible to log where the bogus requests are coming from.