I closed https://bugzilla.redhat.com/1905283 and it's still showing on my dashboard despite the sync at the bottom saying:
Last sync was on May 2 2021, 1:45:29 UTC (7 minutes ago).
So, the last sync timer is something that i need to rework a bit (or more probably a lot). It's basically broken (currently, it means that nothing in the cache is newer, it can be older).
If I am not missing anything, the bug is no longer shown on your dashboard. If it's okay with you, I'll close it and create another tracking issue to improve the last sync time shown.
Sure. :) Yes, I can confirm it's updated now.
Perhaps move all that to a 'status' page that mentions when each thing last synced?
Metadata Update from @frantisekz: - Issue assigned to frantisekz
Unfortunately, this is still an issue. I have many bugs that were closed long ago but are still showing up on my packager dashboard (https://packager-dashboard.fedoraproject.org/dashboard?required_acl=admin&users=rathann) and bugs:
https://bugzilla.redhat.com/show_bug.cgi?id=2118106 https://bugzilla.redhat.com/show_bug.cgi?id=1947732 https://bugzilla.redhat.com/show_bug.cgi?id=2033793 https://bugzilla.redhat.com/show_bug.cgi?id=2004280 https://bugzilla.redhat.com/show_bug.cgi?id=2033168 https://bugzilla.redhat.com/show_bug.cgi?id=1825263
@rathann Is it possible that you've visited the dashboard after a longer time? From what I'd seen server side, it seems so. In this case, the following happened:
Backend stopped syncing your packages to free resources for people who use the dashboard more actively, but kept the old data which you'd seen. By visiting the dashboard now, you'd jumped back into active users and backend placed your packages into sync (which is happening right now and closed bugs seem to be disappearing from your dashboard).
I am still figuring out some ways to improve this scenario. Currently, if you open the dashboard at least once per month, you shouldn't encounter this issue.
@rathann Is it possible that you've visited the dashboard after a longer time?
That's correct. I don't visit often because the dashboard doesn't seem to be useful due to bugs.
From what I'd seen server side, it seems so. In this case, the following happened: Backend stopped syncing your packages to free resources for people who use the dashboard more actively, but kept the old data which you'd seen. By visiting the dashboard now, you'd jumped back into active users and backend placed your packages into sync (which is happening right now and closed bugs seem to be disappearing from your dashboard).
From what I'd seen server side, it seems so. In this case, the following happened:
I see. That's totally confusing. There's no indication in the UI that the data is stale and is about to be refreshed.
Here's one: add a "Bugzilla last cached/refreshed/sync at <datetime>. Next sync in <xxx> minutes/hours/whatever" somewhere at the top so that the user at least knows what's going on in the background and why they're seeing stale data.
Yes, this is one of the issues I'd noticed, hint for frontend that the data are partial wasn't passed from the backend, I am currently looking at it locally and working on a fix. Frontend already has code/functionality in place to indicate "refresh in progress".
Yeah, we used to do this, but the feature was lost during transition to api/v2 last year. @lbrabec we probably should bring it back.
I don't visit often because the dashboard doesn't seem to be useful due to bugs.
Are there any issues apart from this that you've encountered with the dashboard? Please go ahead, and fill issues for anything you find that's broken.
Login to comment on this ticket.