paladox

Im guessing this https://github.com/Icinga/icinga2/commit/1a9c1591c0c13603b1dee6cfb514e6ec7c309450 is the fix.

We have experienced less load since using 2.9. We made sure only one check is run at one time. (this is with nagios-nrpe-server (check_nrpe)) we doin't use icinga2 client.

This should be high priority since without telling you this information everything gets harder to fix the jshint errors.

@vladikoff Currently when it lints the file and finds some errors it does this Actual outcome 19:13:40 Running "jshint:all" (jshint) task 19:13:56 19:13:56 19:13:56 219 | var getDefaultUri = (...

So it tells you the file and line the error is in. But it dosent in grunt-contrib-jshint please could this be changed so it can because grunt-jscs does and grunt-jsonlint...

It has the line the error is comming from but doesn't tell your the file. Also we should add --> to tell you which piece of the code is actually...

I tested with 0.11.3 and it dosent work. So this is supported just the code needs updating.

@vladikoff Could you open the pull since you know how and where to fix it please.

Yes it worked before but it seems to depend on which repo you test for example I am testing it on mediawiki/core which it wont show which file has the...

Yes it seemed to work for me on some repos but on others it didn't. Seems to be a bug then.