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

No suitable finish event for pipe #17037

Closed
polomsky opened this issue Nov 15, 2017 · 2 comments
Closed

No suitable finish event for pipe #17037

polomsky opened this issue Nov 15, 2017 · 2 comments
Labels
question Issues that look for answers. stream Issues and PRs related to the stream subsystem.

Comments

@polomsky
Copy link

  • Version: 8.7.0
  • Platform: linux
  • Subsystem: stream

There is no way to detect that stream.pipe is finished. There is an event finish for writable streams, but it is unusable for specific usecases (writing to process.stdout or process.stderr).
And if I understand it correctly, finish event is not emitted when pipe is called with {end: false}. So I can not simply pipe multiple read streams to the single write stream.

@vsemozhetbyt vsemozhetbyt added the stream Issues and PRs related to the stream subsystem. label Nov 15, 2017
@mscdex mscdex added the question Issues that look for answers. label Nov 15, 2017
@polomsky
Copy link
Author

polomsky commented Nov 21, 2017

After investigation I have found that event unpipe can be probably used for that purpose. Sadly it is not in the 6.x version. Fixed by #11876

@apapirovski
Copy link
Member

Seems like this has been addressed by the OP but if not, please feel free to re-open. Not sure this would get back-ported to v6.x, if it hasn't been already.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
question Issues that look for answers. stream Issues and PRs related to the stream subsystem.
Projects
None yet
Development

No branches or pull requests

4 participants