gulp.src('xxx', {since: gulp.lastRun('xxx')}) issue

[SEIAROTg]

I have such a gulpfile.js:
var gulp = require('gulp');

gulp.task('build:public', function(cb){
    return gulp.src(['src/public/**/*'], {since: gulp.lastRun('build:public')})
        .pipe(gulp.dest('dist/public/'))
        .on('finish', cb);
});

gulp.task('watch:public', function(cb){
    return gulp.watch(['src/public/**/*'], gulp.series(['build:public']));
});

gulp.task('default', gulp.series(['build:public']));

However, when I executed gulp watch:public and changed a file, nothing happened.
Then I guess there may be a time error and changed {since: gulp.lastRun('build:public')} into {since: gulp.lastRun('build:public')-1}. But It still did't work. Then I tried {since: (gulp.lastRun('build:public')/1000-1)*1000}, which works for me.

Is this a bug? And if I want to implement Incremental building, do I have to use such trick?

I am working with Mac OS X 10.10.3, node v0.12.4, npm 2.10.1, gulp 4.0.0-alpha-1, gulp-cli 0.2.0

[phated]

Do you think this is related to gulpjs/undertaker#26 ?

[yocontra]

@SEIAROTg Nope you shouldn't have to do that, definitely a bug or mismatch

[SEIAROTg]

@phated I think it's quite another problem, for it is not only the first calling that have my problem. I guess maybe it's because file timestamp is only accurate in seconds but not in milliseconds

[phated]

@SEIAROTg we are capturing the "last-run" time before the task is run. That is the problem you are encountering. The issue I linked only mentions the first run but it is a problem for every run. See referenced PR on that issue. Also, please note that resolution is 1ms on node 0.11+ https://github.com/phated/default-resolution#default-resolutions

[phated]

I've bumped undertaker to 0.11.1 with the fix for this. Can you please update your deps and try again?

[phated]

Fix in gulpjs/undertaker@96540e3

[SEIAROTg]

@phated It now works fine for me.