title: Why ng-include causing $digest iterations reached?
body: <p>Receiving data by</p>
  
  <pre><code>$scope.$watch("build.idx", -&gt;
    $http.get("/build/" + $scope.build.idx + ".json").success((data) -&gt;
      $scope.build = data
    )
  )
  </code></pre>
  
  <p>ng-include inside ng-repeat</p>
  
  <pre><code>.build-stage
    .row{ "ng-repeat" =&gt; "stage in build.stages" }
      %div{ "ng-include" =&gt; "donoting.html" } # donoting.html is blank
  </code></pre>
  
  <p>first loading page, it's OK. and when changing build.idx, it cause</p>
  
  <pre><code>10 $digest() iterations reached. Aborting!
  Watchers fired in the last 5 iterations: [["fn: function (){var a=d.url(),b=h.$$replace;p&amp;&amp;a==h.absUrl()||(p++,c.$evalAsync(function(){c.$broadcast(\"$locationChangeStart\",h.absUrl(),a).defaultPrevented?h.$$parse(a):(d.url(h.absUrl(),b),g(a))}));h.$$replace=!1;return p}; newVal: 8; oldVal: 7"],["fn: function (){var a=d.url(),b=h.$$replace;p&amp;&amp;a==h.absUrl()||(p++,c.$evalAsync(function(){c.$broadcast(\"$locationChangeStart\",h.absUrl(),a).defaultPrevented?h.$$parse(a):(d.url(h.absUrl(),b),g(a))}));h.$$replace=!1;return p}; newVal: 9; oldVal: 8"],["fn: function (){var a=d.url(),b=h.$$replace;p&amp;&amp;a==h.absUrl()||(p++,c.$evalAsync(function(){c.$broadcast(\"$locationChangeStart\",h.absUrl(),a).defaultPrevented?h.$$parse(a):(d.url(h.absUrl(),b),g(a))}));h.$$replace=!1;return p}; newVal: 10; oldVal: 9"],["fn: function (){var a=d.url(),b=h.$$replace;p&amp;&amp;a==h.absUrl()||(p++,c.$evalAsync(function(){c.$broadcast(\"$locationChangeStart\",h.absUrl(),a).defaultPrevented?h.$$parse(a):(d.url(h.absUrl(),b),g(a))}));h.$$replace=!1;return p}; newVal: 11; oldVal: 10"],["fn: function (){var a=d.url(),b=h.$$replace;p&amp;&amp;a==h.absUrl()||(p++,c.$evalAsync(function(){c.$broadcast(\"$locationChangeStart\",h.absUrl(),a).defaultPrevented?h.$$parse(a):(d.url(h.absUrl(),b),g(a))}));h.$$replace=!1;return p}; newVal: 12; oldVal: 11"]]
  </code></pre>
  
  <p>and when removing ng-include line, it's OK.
  I think it's ng-include causes $locationChangeStart fired, but why?</p>