Not sure if this is the right forum, but after the last failover test, updates to reputation do not show up under the ACHIEVEMENTS menu.

Also, it used to be that my rep. on meta and mse were the same, now the meta is out of sync.

I don't particularly care about these things, but I presume it reflects a code/db change or similar that someone cares about.

I have cleared my Firefox cache and the problem remains.

I have logged in using Chrome and the problem remains.

| |
  • 1
    $\begingroup$ shouldiblamecaching.com $\endgroup$ – user147263 Aug 16 '14 at 17:31
  • $\begingroup$ @900sit-upsaday: I did clear my Firefox cache... Is there some other cache I should be aware of? $\endgroup$ – copper.hat Aug 16 '14 at 17:35
  • 1
    $\begingroup$ I have that happening too, copper.hat, which is why I came to Meta to post as a bug. You did it for both of us. I also have a lingering green box containing $15$, and a lingering red box indicating a "new comment". I've clicked on both dozens of times, they keep reappearing "as new" whenever I refresh the page. Same "accepted" question, same message. This all started before the last "read only" interruption to the site, and persisted after that interruption ended. $\endgroup$ – amWhy Aug 16 '14 at 17:53
  • $\begingroup$ My meta & mse rep. are now the same again. The ACHIEVEMENTS menu is still missing some stuff... $\endgroup$ – copper.hat Aug 16 '14 at 17:56
  • 2
    $\begingroup$ I meant SE cache (which you can do nothing about), not your browser's cache. Various updates tend to go out of whack after failover exercises. $\endgroup$ – user147263 Aug 16 '14 at 18:00
  • 2
    $\begingroup$ @900sit-upsaday: I was thinking locally and acting globally :-). $\endgroup$ – copper.hat Aug 16 '14 at 18:02
  • $\begingroup$ meta.SE: Achievements dropdown not matching actual reputation since read-only time $\endgroup$ – Martin Sleziak Aug 17 '14 at 6:42
  • $\begingroup$ Some items still do not show in the ACHIEVEMENTS list. It does not matter to me, but someone might care. $\endgroup$ – copper.hat Aug 17 '14 at 16:25
  • 1
    $\begingroup$ This is also a symptom of our server-side caching layer - should be fixed now! $\endgroup$ – Jarrod Dixon Aug 18 '14 at 19:19
  • $\begingroup$ @JarrodDixon: Thanks! $\endgroup$ – copper.hat Aug 18 '14 at 19:20
  • $\begingroup$ @Jarrod: So "900" was right? :-) $\endgroup$ – Asaf Karagila Aug 18 '14 at 23:10
  • $\begingroup$ @AsafKaragila: Cache is always a problem for me :-). $\endgroup$ – copper.hat Aug 18 '14 at 23:46
  • $\begingroup$ @copper.hat: Maybe get another job (part time, of course), one that pays in cache? $\endgroup$ – Asaf Karagila Aug 18 '14 at 23:49
  • $\begingroup$ @AsafKaragila: I guess cache has a whole new meaning with Bitcoin and its ilk? $\endgroup$ – copper.hat Aug 19 '14 at 2:48
  • $\begingroup$ I have no idea. I was playing on the similarity to cash. I am not too familiar with cryptocoin lingo... $\endgroup$ – Asaf Karagila Aug 19 '14 at 2:54

Browse other questions tagged .