AngularJS repository marked as being 51 years old #3185

Good point. In this case the broken timestamp is the unix epoch, so it's easy to detect and discard:

https://github.com/angular/angular.js/commit/866346e1ada583daeb649c253516c8f8a879c387.patch

Repos that have this timestamp will simply be cached with false and ignored

I'm wondering why it says 51 years though, as 2020 minus 1970 equals 50. Is that GitHub's <relative-time> element rounding up?

I guess it's rounding up, because we're already in June.

we could use this and filter out the 1990 ones

{
  repository(owner: "angular", name: "angular.js") {
    ref(qualifiedName: "master") {
      target {
        ... on Commit {
          history(first: 5, after: "72fbd48f2a805e789fc574176e7a9a87979418d7 8996") {
            nodes {
              committedDate
              resourcePath
            }
          }
        }
      }
    }
  }
}

Only it if that replaces the current fetchDom request