Improving connect promise handling #134
Merged
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.
A buggy device was closing the socket immediately without sending any data to be parsed so the promise was never resolved or rejected i.e. effectively deadlocking i.e. endless
await telnetClinet.connect()
This PR fixes just
connect
method but probably other methods (send, exec, etc) needs to be fixed too.Generally the problem comes because the underlying socket API is event based and doesn't go well with promises. Another problem comes due lack of control to socket.timeout i.e. we can't cancel it. In overall error handling is really messy and unstable. I did my best with this patch to improve but probably will be better to rewrite everything in a better way.