#134 Closed PRs and bugzillas are shown in the dashboard
Closed a year ago by frantisekz. Opened 2 years ago by rathann.

https://packager-dashboard.fedoraproject.org/user/rathann is showing a lot of outdated items, for example:
https://bugzilla.redhat.com/show_bug.cgi?id=1909558 is closed but still showing under radeontop package.

https://src.fedoraproject.org/rpms/python-xlwt/pull-request/2 is closed but still showing under python-xlwt package.

https://bugzilla.redhat.com/show_bug.cgi?id=1513731 is shown even though I'm not the reporter, maintainer, or even on the Cc list.


https://bugzilla.redhat.com/show_bug.cgi?id=1513731 is shown even though I'm not the reporter, maintainer, or even on the Cc list.

https://src.fedoraproject.org/rpms/mozilla-adblockplus says you are co-maintainer (commit)

You're correct. I thought I removed myself from that package completely years ago. sigh

Thanks for the report!

So, the main issue is this: it seems you've accessed the dashboard after a long time (>14 days since the last visit). The dashboard backend refreshes caches only for users who visited the dashboard at least once in the last 14 days.

However, it leaves the unrefreshed data in the cache after that period expires since your last visit and gives you the old information until it refreshes the data again (which takes up to 2 hours for PRs and bugs, but for bug closes it takes up to 12 hours due to some internal and bugzilla details).

The issue should disappear in ~15 minutes, I've manually refresh the backend caches for packages (python-xlwt, radeontop) you've mentioned, for mozilla-adblockplus, as @churchyard said, you are co-maintainer (you can pin the package to the bottom, or you can type "!mozilla-adblockplus" into the search bar to hide it entirely).

I'll leave this open to track potential garbage collection of old data, or some other fix for this scenario (make backend changes to not ever give outdated data to users? I think it used to work like this, we've changed that for some reasons which I can't remember at all). @jskladan

I think I'm seeing this now. I visited the page after returning from PTO, and it said "refreshing", but I'm seeing lots of bugs that were closed a few days ago.

Same here. I understand it takes time to refresh. But it says "a few minutes", and then even an hour after the spinning wheel stopped you see stale bug information. That's unfortunate. At least, the info should say "can take up to 12 hours" rather than "a few minutes".

So, I've spent some time fixing regressions around this, doing cleanups and improving the backend. Data fetching into the backend cache would never be perfectly on-time, but I believe this could be closed now. If you encounter the issue in the future again, feel free to reopen this.

Relevant backend changes (all deployed into production instance):
- https://pagure.io/fedora-qa/oraculum/c/e2e747053ae4089b65ea6e2dff6003135e7cc21a?branch=master
- https://pagure.io/fedora-qa/oraculum/c/0bb307d1a0dad8c1a9051a32db857200cb7dfa60?branch=master
- https://pagure.io/fedora-qa/oraculum/c/f7aa7bbb5856a9150f7b60047447477e4a0aa361?branch=master
- https://pagure.io/fedora-qa/oraculum/c/5b00a062e6c89a3137315c440ef414e32d6d1b7f?branch=master

Metadata Update from @frantisekz:
- Issue status updated to: Closed (was: Open)

a year ago

Login to comment on this ticket.

Metadata