Added callback to catch an error happening on the socket connection #29
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.
I was having a problem where, whenever I physically disconnected the device connected through the modbus protocol, I'd see an exception on the console but all subsequent petitions I had on a timer never returned thus never received any actual errors on my code and I couldn't recreate the connection.
This solves the issue by adding a callback right where the error is thrown so the user knows it happened and act accordingly.