https://www.drupal.org/project/seckit claims there are 31 open issues, and 8 open bug reports.

https://www.drupal.org/project/issues/seckit shows me only 24 open issues, and 6 open bug reports.

The 'total' values (90 and 36 respectively) are in agreement between the two views.

I suspect this is stale cached content, as the difference matches the number of issues which have been automatically closed during the past week: 2 bug reports, 3 tasks, and 2 feature requests.

All but one of those were closed more than 5 days ago, however, which seems like an unreasonable delay?

Comments

jweowu created an issue. See original summary.

jonathan1055’s picture

jonathan1055 commented

I have noticed the same thing with Scheduler. The project block today says 'All issues: 69 open, 724 total' but the actual counts (using https://www.drupal.org/project/issues/scheduler?categories=All) are 71 open and 726 all, ie two more in both cases. The newest issues are 5 days old (7th March) and 8 days old (4th March). The next newest was created 11 days ago (2nd March).

I no that no issues have been moved out of the Scheduler queue to other queues in recent days, so it would seem that the block as at 13th March is reflecting the position some time between 2nd and 4th March, so at minimum it is 7 days out of date. I recall seeing 69 open issues for quite a few days, which matches this analysis.

Hope that helps.

jonathan1055’s picture

jonathan1055 commented
Related issues: +#2678356: Project Issue Views Broken

This problem could be linked with #2678356: Project Issue Views Broken

drumm’s picture

drumm
he/him
Location NY, US
commented
Status: Active » Closed (duplicate)

#2394175: Remove or emphasise need to log in for search will solve this. Project issue has a special cache for this block, and our customization didn't update the cache clearing completely. Our infrastructure is in a good place now and the customization can be removed.

jonathan1055’s picture

jonathan1055 commented

The https://www.drupal.org/project/scheduler block issue count seems to have corrected itself now. I don't know if any fix was done, or just that something else caused the cache to be refreshed.

https://www.drupal.org/project/seckit is also correct.

Thanks for the explanation and link to the other issue.