Throws when configuring mongo host

geek commented 10 years ago

Mongo host: (127.0.0.1) 
(node) warning: possible EventEmitter memory leak detected. 11 listeners added. Use emitter.setMaxListeners() to increase limit.
Trace
    at ReadStream.EventEmitter.addListener (events.js:179:15)
    at ReadStream.Readable.on (_stream_readable.js:667:33)
    at new Interface (readline.js:124:11)
    at Object.exports.createInterface (readline.js:38:10)
    at read (/Github/hapi-dash/node_modules/prompt/node_modules/read/lib/read.js:45:23)
    at EventEmitter.prompt.getInput (/Github/hapi-dash/node_modules/prompt/lib/prompt.js:502:3)
    at get (/Github/hapi-dash/node_modules/prompt/lib/prompt.js:321:12)
    at /Github/hapi-dash/node_modules/prompt/lib/prompt.js:280:7
    at iterate (/Github/hapi-dash/node_modules/prompt/node_modules/utile/node_modules/async/lib/async.js:134:13)
    at /Github/hapi-dash/node_modules/prompt/node_modules/utile/node_modules/async/lib/async.js:145:25

kidtronnix commented 10 years ago

Have not run into this before. Away from comp but will look into this in the next couple of days. On 25 Aug 2014 16:10, "Wyatt Preul" notifications@github.com wrote:

Mongo host: (127.0.0.1) (node) warning: possible EventEmitter memory leak detected. 11 listeners added. Use emitter.setMaxListeners() to increase limit. Trace at ReadStream.EventEmitter.addListener (events.js:179:15) at ReadStream.Readable.on (_stream_readable.js:667:33) at new Interface (readline.js:124:11) at Object.exports.createInterface (readline.js:38:10) at read (/Github/hapi-dash/node_modules/prompt/node_modules/read/lib/read.js:45:23) at EventEmitter.prompt.getInput (/Github/hapi-dash/node_modules/prompt/lib/prompt.js:502:3) at get (/Github/hapi-dash/node_modules/prompt/lib/prompt.js:321:12) at /Github/hapi-dash/node_modules/prompt/lib/prompt.js:280:7 at iterate (/Github/hapi-dash/node_modules/prompt/node_modules/utile/node_modules/async/lib/async.js:134:13) at /Github/hapi-dash/node_modules/prompt/node_modules/utile/node_modules/async/lib/async.js:145:25

— Reply to this email directly or view it on GitHub https://github.com/smaxwellstewart/hapi-dash/issues/2.

kidtronnix commented 10 years ago

Just triend configuring on my friends mac and everything ran fine. Usually works for me on my Ubuntu machine.

Will look into this further but in the meantime, if you would like to use the app simply paste this into 'config.js' in the root folder, and adjust to your needs:

module.exports = {
    "app": {
        "name": "Hapi Dash",
        "url": "http://localhost:3030"
    },
    "db": {
        "host": "127.0.0.1",
        "port": "27017",
        "name": "hapi-dash"
    },
    "api": {
        "host": "127.0.0.1",
        "port": "3000"
    },
    "coreCreds": {
        "id": "core",
        "key": "QzOJrOTvDq6anyRXZzec3NSQA7rgzih6ort4t62U8P5D5QdK97urJJ5IlKM1rvLO",
        "algorithm": "sha256"
    },
    "gui": {
        "host": "0.0.0.0",
        "port": "3030"
    },
    "email": {
        "service": "Gmail",
        "auth": {
            "user": "sdfds",
            "pass": "dfsa"
        }
    }
}

geek commented 10 years ago

It works now on node v0.10.30. but fails on v0.11.13

kidtronnix commented 10 years ago

Aha, yeah yet to make that upgrade and test.

Will be a problem with the 'prompt' package. On 25 Aug 2014 17:24, "Wyatt Preul" notifications@github.com wrote:

It works now on node v0.10.30. but fails on v0.11.13

— Reply to this email directly or view it on GitHub https://github.com/smaxwellstewart/hapi-dash/issues/2#issuecomment-53287295 .

kidtronnix commented 10 years ago

I have opened an issue with the 'prompt' package about this. Also looking at other node.js cli input packages, not sure if you can recommend any.

kidtronnix commented 10 years ago

Haven't forgotten about this issue. I submitted a ticket with the 'prompt' package. So far no response, at some point I will swap this package out for a more robust one.

RubenCordeiro commented 10 years ago

There are lots of community packages that fail with node v0.11.xx. It's a unstable release after all, most of the time the stream API changes are responsible for the failure. Does anyone use node v0.11 in production? To me, the unstable releases are targeted for community feedback, bug reports and testing.

geek commented 10 years ago

@SynapseR not that its used in production, but its good to be ready for 0.12, which will be out soon, hopefully.

kidtronnix / hapi-dash

Throws when configuring mongo host #2