Refined-github: Age of the repository is miscalculated (19 years old)

[tomkerkhove]

Age of Promitor is miscalculated since it says it's 19 years old.

[sindresorhus]

Related to https://github.com/sindresorhus/refined-github/issues/3185. You have a broken Unix timestamp in the repo.

[kidonng]

Also, try cleaning the extension cache and refresh the page and see if it's correct. I just got 2 years old.

[tomkerkhove]

It's gone but will pop back up I presume, thanks for the quick help

[fregante]

We use the date found on this page: https://github.com/tomkerkhove/promitor/commits/master?after=85bdaae5e96db7943e4582bc1f3c3daa8815989f+782, which is the string 2018-02-04T22:47:41Z

We convert this with new Date('2018-02-04T22:47:41Z'), is it possible that in some cases this might fail?

Do you use Windows?

[fregante]

If it happens again, please take a screenshot with the tooltip, like this, to understand why it's being misparsed.

[tomkerkhove]

I'm using Windows indeed!

[tomkerkhove]

I'll keep an eye on it but it's hidden for now.

[kidonng]

but it's hidden for now.

What do you mean by "hidden"? It doesn't display? Could you please check if there is something like Cannot read property 'split' of undefined in your console? I encountered this issue several times and after cleaning the cache everything backs to normal. Not sure if it is related to this wrong age issue though.

[yakov116]

Could you please check if there is something like Cannot read property 'split' of undefined in your console?

That error is https://github.com/sindresorhus/element-ready/issues/29. On first load sometimes the element is not ready on time

[tomkerkhove]

If it happens again, please take a screenshot with the tooltip, like this, to understand why it's being misparsed.

@fregante from another Windows machine without clearing the cache:

After clearing it doesn't show up but console has this entry:

ℹ️ Refined GitHub → repo-age → Personal token required for this feature

[yakov116]

Hmm, if you have it again can you see if there is an error. Also if you can get the commit its linked to.

[fregante]

It was a token issue then.

[tomkerkhove]

Hold your horses, this was only because I cleared the cache but setting it seems to work.

Why do I need a token for this while it worked before?

[yakov116]

We used to use a method that would load the commits page and detect it from there. Currently we are using an API request, which requires a token.

[fregante]

Discussion may continue on https://github.com/sindresorhus/refined-github/issues/3340