app.prompt.get fails inside asynchronous callbacks on Windows

[jfromaniello]

I have a weird problem that it only happens on windows. I don't know if this is the right place or if I should report it on flatiron/prompt.

Thing is that if I add a simple command like this:

var thing = module.exports,
    app = require("../../app");

thing.run = function(){
    process.nextTick(function(){
        app.prompt.get(["test"], function(e,r){
            console.log("error: " , e, " result: ", r);
        });
    });
};

to an auto generated application (with: flatiron create example cli)

when i execute the application like "simple thing run", I see the prompt message but it seems that it doesn't wait to the user data an inmediately fails with:

[Error: read Unknown system errno 6]
  code: 'Unknown system errno 6',
  errno: 'Unknown system errno 6',
  syscall: 'read' }  

The stack trace is:

prompt: test: error:  Error: read Unknown system errno 6
    at errnoException (net.js:670:11)
    at TTY.onread (net.js:395:21)

Again this only happens on windows.

Do you have any workarround to this? since I guess you do a lot of I/O in jitsu for instance.

Thank you very much, I really like flatiron

[jfromaniello]

More about this... the problem seems to be related to pausing the stdin.
If I remove "stdin.pause()" from prompt.pause, it doesn't fail

[jfromaniello]

I have isolated the problem to the most basic thing, first without flatiron, then without prompt, and I have come to the conclusion that the problem only happens when using the deprecated openStdin() in this line

So, to show the problem, the small code I can show is this:

process.nextTick(function(){
    process.stdin.resume();
    process.stdin.setEncoding('utf8');
    process.stdin.on('error', function (err) {
        console.log(err);
        process.exit();
    });
    process.stdin.on('data', function (chunk) {
        process.stdout.write('data: ' + chunk);
    });
});

process.openStdin();
process.stdin.pause();

This works ok in linux and fail on windows under some circunstances... It has to do with enqueing the prompt in the event loop.

I think we should close this issue here and i will open a new one on flatiorn/prompt.

[jfromaniello]

moved to flatiron/prompt#34