Reemit 'end' event from socket when using MCCP both locally and remote #6
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.
The event 'end' is never emitted when listening from a client, using MCCP on remote and local.
This is a bit hacky, but I didn't find any other solution.
Should have been done in MCCP.js, but didn't find any good way.
I don't really know what the real problem is, could be the stream is in the
middle of expecting to decompress when it receives an 'end', and it will be ignored?
Test code: