buffer() not handling stream errors? about gulp-util

[yocontra]

@stu-salsbury Misunderstanding about how streams work I think. If you want to listen to an error on the inp stream you should add an error event listener to that stream. The callback for the buffer stream has nothing to do with error events up or downstream

[yocontra]

@stu-salsbury err is always null btw https://github.com/gulpjs/gulp-util/blob/master/lib/buffer.js#L8

[laurelnaiad]

I'm listening for specific errors along the way in the pipe and attempting to handle them without quitting the pipeline -- I was never actually relying on the err arg in the buffer callback, which is I suppose how I never realized it isn't populated. Something seems to have changed recently with respect to whether the callback happens at all. Perhaps that's on my side, I have a lot going on. I will continue to investigate. Thanks.

[yocontra]

@stu-salsbury If an error event happens then streams get unpiped, and thus the buffer plugin has nothing to buffer and will never call the callback. Use something like gulp-plumber to disable that node core behavior

[laurelnaiad]

I'm already using gulp-plumber. I think the issue has something to do with a change to how I'm using lazypipe, which doesn't get along well with gulp-plumber. I'm going to try to backtrack and figure out where it went south.

[laurelnaiad]

If was a fundamental issue with the combination of gulp-plumber, lazypipe and gulp-if. I took out gulp-if/lazypipe and replaced them with gulp-filter and all is well.