Created helpful error message when using @each on an array that does not return objects
Don't push childViews if undefined/invalid (issue #2967)

Since 3a16e2821d021a2c88ac290516825ca3b0cafa62, pushObjects throws an error when provided with null or undefined.

Checking the childViews property for compatibility with the pushObjects method prior to calling pushObjects. Will not attempt to push invalid objects.
Simplified to existence check

As suggested by @stefanpenner
Fix typos in the inline testing package docs
Merge pull request #2998 from kategengler/fix-inline-testing-doc-typos

Fix typos in the inline testing package docs
Merge pull request #2975 from realityendshere/fix-childview-pushobjects

Don't push childViews if undefined/invalid (issue #2967)
fix code styling for consistency
Merge pull request #2999 from tchak/fix-style

fix code styling for consistency
use Ember.K for consistency

Unless there's a reason behind using just `function() {}`, it seems more reasonable to use Ember.K for consistency
upload prod builds to s3
Merge pull request #3003 from fivetanley/upload-prod-builds

upload prod builds to s3
Merge pull request #3001 from raulbrito/patch-3

use Ember.K for consistency
Fix: didInsertElement was fired twice

Happens when a ContainerView is created during the didInsertElement event of
its parent ContainerView
Support indeterminate property in checkboxes
Merge pull request #3004 from alexspeller/bind-indeterminate-attribute-in-checkbox

Support indeterminate property in checkboxes
Fixed incorrect example of multi-arg registerBoundHelper
Documentation for sendEvent and doc change in removeListeners
Use the original arg length of wrapped CP funcs, still call the wrapper

ComputedPropertyPrototype.set analyzes the length of CP arguments to
decide how the CP function should be called. Since the wrapper (which
sets up _super) handles arbitrary arguments, the original function (at
wrappedFunction) should be inspected for .length. The wrapper, however,
should still be called when performing the set (ensuring that _super is
present).

Fixes #2890
Expose `options` arg in `debugger` HB helper

Without this, you can't look up template data and other important pieces of data. (`arguments` is optimized away in Chrome since the function makes no other reference to it)
Merge pull request #3013 from mixonic/2890

Use the original arg length of wrapped CP funcs, still call the wrapper