-
-
Notifications
You must be signed in to change notification settings - Fork 28
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
Add failing pumpify test #17
Conversation
Thanks. That does indeed seem wrong. Will take a look today |
This was a pumpify bug. Fixed it there and added a test. Can you verify it works for you now if you reinstall all the deps? |
@mafintosh awesome! I thought that might be the case. It seems like problem still exists. I've bumped the pumpify version in the devDeps to show in this reduced case. |
It seems that using 3 |
Hey @mafintosh - anything else I can help with here? |
Friendly ping |
@phated turns out this was an issue in pumpify, fixing it there. |
@phated should be fixed now! for good hopefully :) i ended up moving the tests to pumpify as it was an issue there. |
Awesome! Thanks @mafintosh 😸 |
Hey @mafintosh, I just ran into this issue within the published release of gulp 4. It seems that using pumpify with end-of-stream swallows any errors that happen in the middle of the pumpify stream and instead emit a "premature close" error.
I've created a simplified reproduction case in the tests but I'm not too sure which module needs the fix or what to actually fix. Thoughts?
cc @erikkemperman