On my dashboard I have 4 "Issues for " blocks. (Views, Panels, Ctools, Contextual Administration in case someone wants to replicate exactly). In the process of adding these, one of the existing blocks would occasionally change back to tracking drupal core when adding a new block. I had instances where it worked properly, and instances where it did not, so the bug seems intermittent. (or it's only happening as the block number becomes even, seemed to happen on the 2nd and 4th blocks but not the third, don't know if this was just coincidence.

Comments

lisarex’s picture

lisarex commented
Project: Drupal.org Redesign » Drupal.org customizations
Version: » 6.x-3.x-dev
Component: Dashboard » Code

Is this still happening?

dww’s picture

dww
we/he/they
commented
Project: Drupal.org customizations » Project issue tracking
Version: 6.x-3.x-dev » 6.x-1.x-dev
Component: Code » User interface
Status: Active » Postponed (maintainer needs more info)
Issue tags: +dashboard

This block is provided by project_issue itself, not drupalorg -- moving to a more appropriate queue.

However, I'm also wondering if this is still happening. Please reopen and set to "active" or "works as designed" as appropriate.

Thanks,
-Derek

markhalliwell’s picture

markhalliwell
Primary language English
commented
Title: "Issues for <module>" block intermittently reverts to tracking drupal core. » "Issues for <project>" statistics block showing incorrect information
Version: 6.x-1.x-dev » 7.x-2.x-dev
Issue summary: View changes
Status: Postponed (maintainer needs more info) » Active
Issue tags: +project page

Considering this issue seems to be abandoned but also semi-related (incorrect information being shown) to what I'm encountering, I'm re-purposing.

On https://www.drupal.org/project/bootstrap, this block shows there are:

248 issues open (link), when in fact there are only 157.
88 bugs open (link), but there are only 57.

At first I thought it may just be a caching issue maybe? But it's been about 24hrs, is there something more going on here?

drumm’s picture

drumm
he/him
Location NY, US
commented

These blocks are cached, maybe too aggressively. bootstrap's numbers are currently 156 & 56.

We can proactively clear the cache when an issue changes status. Or Drupal.org has https://www.drupal.org/project/render_cache; we could put something like last issue update time in the key, although that would add a query to figure that out.

markhalliwell’s picture

markhalliwell
Primary language English
commented

Hrm. Yeah, that must have happened sometime today; maybe during the recent deployment?

Idk what a great solution is per se, I just did a massive amount of IQ grooming last night and noticed there wasn't any change to these blocks afterwards... made it hard to really gauge just how much I did. I did try to update the project page to see if maybe that would clear out any cache, but that didn't seem to work... could be a possible solution?