Bug: Metrics take a minute to update on Workspace creation

[isabensusan]

Describe the bug

During a demo with the Appwrite team, we had the situation where Tessa setup her workspace on the call, but when she finished setup and went to take a look at her dashboard, all metrics where at 0. She had to do a hard refresh to start seeing the correct numbers.

@bdougie mentioned this was a recurring issue

Suggested solution

Can we setup a loading or indexing state? UI wise we should:

• Use the loading component to blur out the metrics (skeleton wrapper) I don't want the user to see a 0 while it's loading, since it looks more broken than anything.
• Add a toast on the top right corner that shows only on first load to let users know that indexing for the first time takes a minute.

Copy for a potential toast

Title: We're fetching your data Content: This shouldn't take longer than 5 minutes. If it does, try doing a hard refresh on the page or open a support ticket

Where support ticket opens up a bug in the repo (or a discussion?)

Steps to reproduce

1. Create a new workspace
2. Add repositories (preferably, some you haven't used in other workspaces before)
3. Click on Update Workspace
4. Navigate to the dashboard and see the metrics at 0

Browsers

No response

Additional context (Is this in dev or production?)

No response

Code of Conduct

• [X] I agree to follow this project's Code of Conduct

Contributing Docs

• [X] I agree to follow this project's Contribution Docs

[github-actions[bot]]

Thanks for the issue, our team will look into it as soon as possible! If you would like to work on this issue, please wait for us to decide if it's ready. The issue will be ready to work on once we remove the "needs triage" label.

To claim an issue that does not have the "needs triage" label, please leave a comment that says ".take". If you have any questions, please reach out to us on Discord or follow up on the issue itself.

For full info on how to contribute, please check out our contributors guide.

[nickytonline]

We'd have to start in the API to surface an indexing state, so that the UI can respond accordingly.

[jpmcb]

Can we setup a loading or indexing state?

...

We'd have to start in the API to surface an indexing state

On the API side, there's nothing to load or index. It should be all almost immediately available since we're aggregating all this data in real time from buckets of events we already have. If I make a workspace with some repos, that workspace is successfully created, all that data should be there on the next workspace call.

I think I know what the problem is: the http-cache headers are probably kicking in which is why you won't see an update unless you hard refresh / clear you local-storage / cookies. We definitly want the http-cache headers ... but if there was a way that the client could ignore those caches on certain scenarios, that would be super ideal.

Otherwise, we'd have to start exploring lifting the caching out of the http layer and into the API.

[nickytonline]

I think you can pass additional headers in a fetch call to ignore the cache, but I wonder if it makes sense to use the http cache for this particular scenario. But we also use the useSWR hook. It looks like we can pass the useSWR fetcher headers as arguments. See https://github.com/vercel/swr/discussions/545