Coffee and Code

I believe there is a bug in `tasks/grunt-karma.js` where the `background` option is checked on `this.data` instead of `data`. Making the change does not fix my problem though so I...

That looks like a bug was introduced in as much as I know about the internals. I believe `this.data.background` should have been `data.background` on line 34 of tasks/grunt-karma.js

Sorry @devmao, no dice. Tracing the code shows that line 34 evaluates to `null` or `undefined` (I forget which) instead of the boolean set in the Grunt task options.

Thanks will do. I'll post back how it goes. I was having some issues after changing just `this.data` before, but I'll make sure to check with the new releases first.

Unfortunately I think this is a larger issue. I'm not sure what sets `this.data`, but the bug that was just fixed means (at least for me so far) that an...

@mzgol could you post your karma.conf.js file as well?

Thanks, I'll play around with this over the weekend in a fresh project if I get time and see if anything has changed. - Jon On Wed, Jul 3, 2013...

I still couldn't get it to work in the previous project, but I started one from scratch and it's working so far: https://github.com/CoffeeAndCode/grunt-karma-test I would have to add livereload, connect,...

A possible option would be to utilize the `accept_env_factor` property when setting up Duo, by passing in the code during the Ansible run. https://www.duosecurity.com/docs/duounix