Empty wakatime card

[Grayson-code]

Describe the bug
So the wakatime stats card doesnt show the wakatime stats even with the correct username, its for my profile readme and the github-readme-stats readme. is it just me or for everyone
Expected behaviour
Show the wakatime stats of all users

Screenshots / Live demo link (paste the github-readme-stats link as markdown image)

and

Additional context
Add any other context about the problem here.

[NChechulin]

No, this is not wakatime bug, apparently.
Github Caches images (you can hover on it and the tooltip will show that the image is actually located on Github servers).

After some research, I found that Github respects the cache-control HTTP header. Therefore, the solution could be to include a Cache-Control: no-cache header on the server side.

Currently it's set to cache-control: public, max-age=14400(which is 4 hours).

So it's not really a bug, it's a delay of <= 4 hours.

I suppose deciding on cache policy is up to the project owner/contributors.

[Grayson-code]

No, this is not wakatime bug, apparently. Github Caches images (you can hover on it and the tooltip will show that the image is actually located on Github servers).

After some research, I found that Github respects the cache-control HTTP header. Therefore, the solution could be to include a Cache-Control: no-cache header.

Currently it's set to cache-control: public, max-age=14400(which is 4 hours).

So it's not really a bug, it's a delay of <= 4 hours.

I suppose deciding on cache policy is up to the project owner/contributors.

oh

[rickstaa]

@NChechulin is correct. We use caching to lower the load placed on the public Vercel instance. Since GitHub limits the number of requests made to the GraphQL API made in one hour, we are using several personal access tokens (PATs) to fulfil demand.

When demand for the public Vercel instance increases, we can add an extra PAT (i.e. create a new GitHub account) or increase the cache. The original caching time was 2 hours but we increased it during the last service downtime (see 9d2bfd9 and #1471). We think that 4 hours and 10 PAT is a good trade-off for most people. As a result, it takes 4 hours for your Wakatime card to update. @Grayson-code, @NChechulin can you explain why 4 hours do not work for you?

If you want instant updates, you can also fork this project and change the cache as was done in 9d2bfd9 and deploy your own Vercel instance.

Apart from that, please be aware that we currently only accept Wakatime profiles that are public.

[rickstaa]

Nevertheless, your card should show results after 4 hours. I just checked my card, and it seems to work when I set my profile to public. The current implementation does not work with private profiles since we are not using secret API keys. As a result, no activity is shown when my profile is private since we can not fetch personal data. I think you are experiencing the same problem as your profile is not public (see https://wakatime.com/@graysoncode). I agree that the documentation needs to be updated to make users aware of this behaviour.

[rickstaa]

I added #1794 to fix the confusion.

[Grayson-code]

Thank you i have made the account public! and it works!