Meta Stack Exchange is where users like you discuss bugs, features, and support issues that affect the software powering all 158 Stack Exchange communities.

What is meta?
Here's how it works:
  1. Any Stack Exchange user can ask a question
  2. The community provides support, votes on ideas, and reports bugs
  3. Your voice helps shape the way Stack Exchange operates

The user activity overview dialog that you see when you mouse over your user name at the top of the page normally displays the reputation that you gained on the current day. This was handy for telling if you were close to the reputation cap.

I just noticed that the dialog is now displaying the combined reputation that I gained yesterday and today (3.5 hours into a new day).

Activity Overview

Was this an intentional change to display the reputation gained in the last 24 hours, or is this a display/caching bug?

share|improve this question
I also have same issue. – Somnath Muluk Mar 15 '12 at 10:08
up vote 28 down vote accepted

We run a job once a day to reset these totals to 0 for everyone exactly at UTC midnight, unfortunately when deploying network-wide changes to fix associations permanently some servers went absolutely batshit crazy due to a few race conditions. Our status dashboard looked like a Christmas tree for the better part of a hour. Hopefully though, you saw very few errors during this.

The reputation dropdown is driven off of 5 columns in the database from your user record: Reputation, ReputationWeek, ReputationMonth, ReputationQuarter and ReputationYear. The way we maintain these is incredibly simple, a trigger. When Reputation changes, that same delta is applied to all the other columns. When the interval rolls over, the job running at UTC midnight resets whatever intervals are changing to 0 for everyone in a simple update.

Due to the server farm FREAKING THE HELL OUT, that didn't happen. Honestly, it's just not worth fixing IMO, since it only affects the day interval and will fix itself tonight in the rollover.

If it's that important to people we can fix the totals for today, but unless there's a large cry to do so, I'll spend time on bigger fish today (e.g. showing actual rep change from when a user is deleted in a sensible way, or post migrations as "migrated" instead of "removed" in the rep history).

share|improve this answer
Middle year Christmas - isn't this wonderful? :) Anyway - can we tell (in a comment) to all those reporting here today about this issue that it will resolve itself by tomorrow? – Shadow Wizard Mar 15 '12 at 11:35
Nah, I wouldn't worry about it if it's going to right itself at midnight UTC. Thanks for the reply. – Bill the Lizard Mar 15 '12 at 11:43
Yes, stick to the big fish – David Heffernan Mar 15 '12 at 12:49
@ShaDowWizArd - absolutely, if it comes up close as a duplicate of this. – Nick Craver Mar 15 '12 at 14:18
Well, about 5 I counted and I think there are more that get deleted quicker than I can notice. But still, I agree it can wait. Thanks! – Shadow Wizard Mar 15 '12 at 14:25
Ah ha, was that why things seemed to get sluggish for a bit last night? – Tim Stone Mar 15 '12 at 18:02
@Tim - Yup, some Init() code on StackAuth/API v1 was running many, many many times due the timeout/retry mechanism in the pipeline - producing some very bad side-effects. Once we sorted out that memory gobbling (literally all of it) problem, everything settled down. – Nick Craver Mar 16 '12 at 0:31
Ouch, that sounds pretty nasty. Credit to the team though - all I noticed was the brief period of slow response times, so seems things held together pretty well under the circumstances. – Tim Stone Mar 16 '12 at 0:40
"post migrations as 'migrated' instead of 'removed'"; yes please! Does this mean that it may come sooner than you previously indicated? – ben is uǝq backwards Mar 18 '12 at 16:34
@Ben - Yup, it's in place now. Anything migrated to another site and deleted will now show as "migrated" in your rep history. – Nick Craver Mar 18 '12 at 17:15
Looks like it happened again last night; more Christmas lights at midnight? – Martijn Pieters Jun 6 '12 at 9:01
@MartijnPieters - yep, the scheduler service ate it about 12 hours ago, we're looking into what happened – Nick Craver Jun 6 '12 at 12:09

You must log in to answer this question.

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