{"action":"created","issue":{"url":"https://api.github.com/repos/foreverjs/forever/issues/767","repository_url":"https://api.github.com/repos/foreverjs/forever","labels_url":"https://api.github.com/repos/foreverjs/forever/issues/767/labels{/name}","comments_url":"https://api.github.com/repos/foreverjs/forever/issues/767/comments","events_url":"https://api.github.com/repos/foreverjs/forever/issues/767/events","html_url":"https://github.com/foreverjs/forever/issues/767","id":112650605,"number":767,"title":"Forever erroneously pops up console window when executing child process calls","user":{"login":"jonrhall","id":5432730,"avatar_url":"https://avatars.githubusercontent.com/u/5432730?v=3","gravatar_id":"","url":"https://api.github.com/users/jonrhall","html_url":"https://github.com/jonrhall","followers_url":"https://api.github.com/users/jonrhall/followers","following_url":"https://api.github.com/users/jonrhall/following{/other_user}","gists_url":"https://api.github.com/users/jonrhall/gists{/gist_id}","starred_url":"https://api.github.com/users/jonrhall/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/jonrhall/subscriptions","organizations_url":"https://api.github.com/users/jonrhall/orgs","repos_url":"https://api.github.com/users/jonrhall/repos","events_url":"https://api.github.com/users/jonrhall/events{/privacy}","received_events_url":"https://api.github.com/users/jonrhall/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":2,"created_at":"2015-10-21T18:27:29Z","updated_at":"2016-04-01T09:09:13Z","closed_at":null,"body":"Working with Forever, trying to stand up a fairly simple node server which makes remote calls to a C# client. If you run the script/server directly with Node, no popup console windows will appear, but when run with Forever, every time the server wants to execute a remote command, a console window appears and then disappears after the remote command is finished.\r\n\r\nReproducible on:\r\n-Windows 7 Ultimate\r\n-Node v0.12+ or v4.0+\r\n-npm v3\r\n-Forever 0.15.1\r\n\r\nTrivial code example that replicates the error:\r\n\r\n\tvar http = require('http'),\r\n\t    exec = require('child_process').exec,\r\n\t    server;\r\n\t\t\r\n\tserver = http.createServer(function (request, response) {\r\n\t\tvar child;\r\n\t\t\r\n\t\tif (request.url != '/') {\r\n\t\t\tresponse.writeHead(404);\r\n\t\t\treturn response.end();\r\n\t\t}\r\n\r\n\t\tresponse.writeHead(200, {\"Content-Type\": \"text/plain\"});\r\n\t\t\r\n\t\tchild = exec('ping localhost -n 2', {}, function(error, stdout, stderr) {\r\n\t\t\tresponse.write(stdout);\r\n\t\t}).on('close', function(code) {\r\n\t\t\tresponse.end();\r\n\t\t});\r\n\t});\r\n\r\n\tserver.listen(8000);\r\n\r\nIs there some kind of bug with Forever itself, or is this some configuration option that I'm missing?"},"comment":{"url":"https://api.github.com/repos/foreverjs/forever/issues/comments/204322073","html_url":"https://github.com/foreverjs/forever/issues/767#issuecomment-204322073","issue_url":"https://api.github.com/repos/foreverjs/forever/issues/767","id":204322073,"user":{"login":"jpek42","id":6492545,"avatar_url":"https://avatars.githubusercontent.com/u/6492545?v=3","gravatar_id":"","url":"https://api.github.com/users/jpek42","html_url":"https://github.com/jpek42","followers_url":"https://api.github.com/users/jpek42/followers","following_url":"https://api.github.com/users/jpek42/following{/other_user}","gists_url":"https://api.github.com/users/jpek42/gists{/gist_id}","starred_url":"https://api.github.com/users/jpek42/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/jpek42/subscriptions","organizations_url":"https://api.github.com/users/jpek42/orgs","repos_url":"https://api.github.com/users/jpek42/repos","events_url":"https://api.github.com/users/jpek42/events{/privacy}","received_events_url":"https://api.github.com/users/jpek42/received_events","type":"User","site_admin":false},"created_at":"2016-04-01T09:09:13Z","updated_at":"2016-04-01T09:09:13Z","body":"We were able to work around this by creating a separate small EXE (on Windows), which does the exec of the child program, setting the correct flags to avoid the process window. I'm not sure that the above comment is the same issue, as our child process was actually running."}}