Danny Krainas

This is the default behavior for helm now and can probably be closed, see kubernetes/helm#1142 From the PR's author: > Just as a reminder: this PR changes the default behaviour...

@nktnet1 as a quick fix: by omitting any filter to node-netstat, you can apply your own advanced filtering strategy in the item handler. I could also look at adding support...

@nktnet1 do you currently receive an error from node-netstat when netstat is missing? I would guess something like an ENOENT error? Telling the user they must install some package is...

@nktnet1 understood - I will look to make sure it errors cleanly if netstat isn't installed or in PATH.

@nktnet1 I see the issue - you need to add a `done` handler to your netstat options and check the error returned. Here's an example: ``` netstat.parsers.dummy = 'dummy'; netstat.commands.dummy...

1) I'm going to have to say no for now and I wouldn't accept a PR change for that at the moment. It would be too much of a breaking...

Thanks for the suggestion! I will be including promises with the next major revision

Maybe something like docker registry uses to initialize its storage driver? Unmarshal the parameters into a `map[string]interface{}` and the driver's factory func handles verifying the correct values are provided. ```...

Just wanted to bump in case this hasn't gotten eyes because of the build failure: looks like the build failed because of the DNS DDoS that was going on at...

I dug into this and it looks to be on ZK's end, it doesn't send the event. I modified go-zookeeper to log the `res.xid` from ZK and then created a...