In the Users page (either the quarter view or year view), when I hover over Barrie England's rep, the popup shows the amount twice (along with the total rep):

enter image description here

In the week, month, or all views, or for other users, the popup is calculated correctly:

enter image description here

Before you sigh in disbelief at my pettifogging, check out the voters tab or the editors tab, in any view except all. Every single user has their total reputation no less than three identical times on the popup, even where it says it's the rep for the month or week or whatever:

enter image description here

Sigh all you want.

Edit: Hovering over Barrie's rep in the quarter view of the rep user tab still brings up a buggy popup:

![](http://i.stack.imgur.com/v2gHI.png)

Further edit: And now that's about to be fixed too.

share
    
I seldom sigh in disbelief anymore at pettifogging. –  Robusto Mar 20 '12 at 16:11
2  
I'm a great believer in the idea that apparently trivial glitches may be of interest to devs, because they may be indicative of more serious problems "below the waterline". Anyway, in checking this one out (not that I disbelieved you - I just wanted to get a feel for it), I ended up clicking on the "editors" tab for the first time ever. And realised that my ranking there is noticeably lower than on rep or votes, so I guess I should shake a leg and make a bit more effort in that respect (thanks for nothing, @Daniel! :) –  FumbleFingers Mar 20 '12 at 18:07

1 Answer 1

up vote 2 down vote accepted

See the answer to Hover popup shows wrong/duplicate rep for week/month/etc in user profile page, the question I posted on MSO after I realized the bug was on every site:

Thanks, this will be fixed in the next build.

For those of you who don't understand the terminology used in the quoted answer, it means the bug will soon be squashed.

share
1  
Ah, right. So status-completed is just an optimistic way of looking at things? I think there's a flaw in the logic there. Suppose the devs think they've fixed it, but actually they fail? Perhaps we should have another tag called status-really-completed that the OP (or anyone else, come to that) could add once we've seen that it really is fixed. –  FumbleFingers Mar 22 '12 at 0:39
    
@Fumble: perhaps the status-completed tag should read we think we've fixed this one, but no guarantees? –  TimLymington Mar 22 '12 at 10:54
    
... or more precisely, "we think we will have fixed this one soon, but no guarantees"? I suppose if the relevant dev doesn't assign the flag until after he's made a change and seen that it seems to be fixed, it's a reasonable approach. But not if the dev just sets the flag to mean "Okay - I've seen the bug report. I'll remember and fix that tomorrow". Then goes off sick for a while, and it slips through the net. –  FumbleFingers Mar 22 '12 at 13:12
    
@FumbleFingers There's a difference between status-completed (that is, re-coding is done) and status-implemented or whatever the equivalent is in SO (that is, the users can use the re-coded software). –  Andrew Leach Mar 27 '12 at 16:02
1  
@Andrew Leach: Sounds good in principle, but I note that if I search for [status-completed] here on meta, I get lots of hits. Sadly, [status-implemented] gets none at all! –  FumbleFingers Mar 27 '12 at 16:06
    
In this case it ended up that they didn't fully fix it the first time, and had to try again. –  Daniel Aug 30 at 17:39

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .