unwatch produces NaN for last position

[erik-stephens]

unwatch() doesn't seem to work very well. I don't nodejs very well, so having a difficult time understanding the async.reduce() call. Maybe a name clash with start? For anything but the first iteration, start becomes undefined which causes this to go sideways.

$ cat dood.js
Tail = require('tail-forever');
tail = new Tail("/tmp/dood", {start: 0, bufferSize: 6});
tail.on("line", function(line) { });
tail.on("error", function(error) { console.log('ERROR: ', error); });
function unwatch() {
  console.log('POS:', tail.unwatch());
}
setTimeout(unwatch, 1000);

As long file is less than buffer size, seems ok...

$ echo foo > /tmp/dood
$ node dood.js
POS: { inode: 137561, pos: 4 }

but as soon as more than one chunk is read, the last known position goes NaN:

$ echo foobar > /tmp/dood
$ node dood.js
POS: { inode: 137561, pos: NaN }

[megastef]

I think the .js file is generated by coffee script. It would be better to search the "bug" in the .coffee file. In this case it might help to "compile" the .coffee file again with the current version.

@mingqi will you maintain this repository and accept pull requests/publish to npm?

[megastef]

I made some tests in my fork, and setting the option "bufferSize: -1", did not produce NaN.

[mingqi]

@megastef yes, I maintain this repository and accept PR to npm

[megastef]

@mingqi Thank you very much for the quick merge!