I suspect a bug in our git implementation. For one of the packages, I'm
getting an error about an object with a given SHA not been found. I will
file a bug about that. That said, all kinds of errors can occur when you're
dealing with a non-curated source of packages. So we have to be tolerant.
On Apr 11, 2014 3:30 PM, "Devon Carew" <notifications@github.com> wrote:

> In ide/app/lib/package_mgmt/bower_fetcher.dart:
>
> > +    return deps;
> > +  }
> > +
> > +  Future<String> _readRemoteSpecFile(_Package package) {
> > +    final String url = package.getUrlForDownloading(_packageSpecFileName);
> > +    return html.HttpRequest.getString(url)
> > +        .catchError((e, s) =>
> > +            _logger.info('Error reading spec file for ${package.name}: $e'));
> > +  }
> > +
> > +  Future _fetchPackage(_Package package) {
> > +    return _packagesDir.createDirectory(package.name, exclusive: true)
> > +        .then((dir) {
> > +      return _git.clone(package.getUrlForCloning(), dir, branchName: package.branch)
> > +          .catchError((e, s) =>
> > +              _logger.severe('Error cloning package ${package.name}: $e'));
>
> OK, makes sense. It's crazy that the polymer dependency graph has a bad
> dependency currently. I guess bower is by nature very fault tolerant?
>
> —
> Reply to this email directly or view it on GitHub<https://github.com/dart-lang/spark/pull/1523/files#r11554718>
> .
>