Tabs broken in 0.5 and 0.6? (working in 0.4)

[pongells]

Hi all, I get the following error:

TypeError: Cannot read property '$parent' of undefined
    at link (http://localhost:8081/js/bootstrap/ui-bootstrap-tpls-0.6.0.js:2739:51)
    at nodeLinkFn (http://localhost:8081/bower_components/angular/angular.js:4582:13)
    at delayedNodeLinkFn (http://localhost:8081/bower_components/angular/angular.js:4735:11)
    at compositeLinkFn (http://localhost:8081/bower_components/angular/angular.js:4191:15)
    at nodeLinkFn (http://localhost:8081/bower_components/angular/angular.js:4576:24)
    at http://localhost:8081/bower_components/angular/angular.js:4736:13
    at nodeLinkFn (http://localhost:8081/bower_components/angular/angular.js:4576:24)
    at delayedNodeLinkFn (http://localhost:8081/bower_components/angular/angular.js:4735:11)
    at compositeLinkFn (http://localhost:8081/bower_components/angular/angular.js:4179:15)
    at nodeLinkFn (http://localhost:8081/bower_components/angular/angular.js:4576:24) <ul class="nav {{type &amp;&amp; 'nav-' + type}}" ng-class="{'nav-stacked': vertical}" tabset-titles="!tabsAbove"> angular.js:5930

it appears tabsetCtrl.$scope is undefined..

.directive('tabsetTitles', ['$http', function($http) {
  return {
    restrict: 'A',
    require: '^tabset',
    templateUrl: 'template/tabs/tabset-titles.html',
    replace: true,
    link: function(scope, elm, attrs, tabsetCtrl) {
      if (!scope.$eval(attrs.tabsetTitles)) {
        elm.remove();
      } else {
        //now that tabs location has been decided, transclude the tab titles in
        tabsetCtrl.$transcludeFn(tabsetCtrl.$scope.$parent, function(node) {
          elm.append(node);
        });
      }
    }
  };
}])

any idea what is going on?

[pkozlowski-opensource]

@pongells yeh, we are aware of it, this is basically duplicate of #783. At this point we are not sure if this is due to AngularJS or something is wrong in our directive. @ajoslin I know that you are busy man but it would be totally awesome if you could have a look at #783

[mboudreau]

@pkozlowski-opensource it's not a duplicate, I get exactly the same problem and it has nothing to do with repeaters. I'm utterly confused as to how a glaring problem like this is still at large...