Critical: Step is skipping steps! about step HOT 4 CLOSED

This may be an issue with node -- It appears that the fs.stat callback is getting triggered _before_ the next.parallel() -> process.nextTick() --> check, at least in this specific case (FYI, for some reason I can only get this to happen on the step/test directory. I noticed it because that was a sub-directory of something I was scanning).

from step.

... that's exactly what is happening

var fs = require('fs');

fs.stat( '.', function(){ console.log( 'Stat is done' ); });

for( var i=0; i<100000; i++);

process.nextTick( function(){ console.log( 'Next Tick' ); } );

Stat is done shows up first... similarly, the check() pushed to nextTick is getting triggered late and causing a double-execution of next.apply(...). Step is in a race condition with the file-system here :)

from step.

I think that this is not a problem of Node.
check() is called more one times than the size of the group.
Probably, at the last twice, pending is 0.
Therefore localCallback() may be called twice.
I think that it needs guard.
workaround:

@@ -95,6 +95,7 @@ function Step() {

     function check() {
       if (pending === 0) {
+        --pending;
         // When group is done, call the callback
         localCallback(error, result);
       }

from step.

I don't remember if this was fixed? If this is still an issue please re-open. Also see #24

from step.