Ember.js 2.0 - changing property twice in one render drop alert

I am developing an app with the current beta version of Ember 2.0 (beta 1) and started seeing this disclaimer:

You changed XXX twice in the same render. This was unreliable in Ember 1.x and will be removed in Ember 2.0

It looks like the offenders are computed properties that are recalculated multiple times because their dependent key is updated multiple times in the same startup cycle. However, the stack trace for deprecations does not return to any of my app codes, and I thought this was something that Ember should have silently taken care of me anyway anyway.

Is this something I need to actively fix my application code prior to upgrading to v2.0 when it was released, or is it more likely an "internal" disclaimer? If I need to make changes, are there any generic anti-patterns or gotchas I should be looking for that might cause this error?