I this question, I replied to a comment. The comment I replied to then appeared below my comment with a timestamp in the future:

enter image description here

The comments will now just appear out of sequence, but at the time the timestamp was in the future.

This has been posted a couple of times in the past, but it appears to be happening again.


Update: There have been reported incidents of this also occurring in other areas where timestamps are generated, such as the closed question notices and in chat.

share|improve this question
11  
Really, 'in 31 seconds'? Oi, someone nicked my timemachine! –  Martijn Pieters Nov 21 '12 at 16:16
4  
Time is ‮ !gnilevarnu –  amanaP lanaC A nalP A naM A Nov 21 '12 at 16:22
    
Now my head hurts, thanks >.> –  Rawling Nov 21 '12 at 16:24
4  
Who knew they even had code that compensated for times past the current time... Planning for something are we Stack Exchange? Spill the beans! –  animuson Nov 21 '12 at 16:24
1  
@amanaPlanaCAnalPAnaMA Hilariously, in IE8 View Source, your comment causes a <naps/> tag to appear instead of a </span>. –  Rawling Nov 21 '12 at 16:27
    
@Rawling hehe it used to do that in the Chrome Inspector too, but it seems like they fixed that lol –  amanaP lanaC A nalP A naM A Nov 21 '12 at 16:28
    
There's definitely something wonky going on. The transcript of a chat I just had has the message order flipped. And another room's info says the last message was posted -35 seconds ago. That's at least the weird stuff I see. Not sure if that's just a local thing though. –  Bart Nov 21 '12 at 16:30
1  
By the way, these comments' ids ordering is right. Weird. –  raina77ow Nov 21 '12 at 16:35
3  
+1 for mentioning the cock blender –  kbok Nov 21 '12 at 17:04
    
@Bart seems likely. –  R. Martinho Fernandes Nov 21 '12 at 17:07
    
@amanaPlanaCAnalPAnaMA Using the <naps/> html there are you? –  Richard J. Ross III Nov 21 '12 at 17:08
8  
They've build timemachines and precognitive robots, and they still haven't fixed the damn review??? –  Yannis Nov 21 '12 at 17:09
2  
@Yannis: And it seems they don't plan to, otherwise they would've sent the fix back in time. –  Xeo Nov 21 '12 at 17:10
    
it's the end of the world coming, 2012 is almost over –  Sam I am Nov 21 '12 at 17:18
1  
Very possibly related: meta.stackoverflow.com/questions/156383/… –  Robert Harvey Nov 21 '12 at 17:30
show 2 more comments

3 Answers

up vote 22 down vote accepted

This was actually caused by the hurricane failover and our silly decision to seize FSMO roles. When you do this to an AD environment, you have to setup the new PDC Emulator master as the authoritative time source on the network.

We, uh, didn't do that, so as a result all manner of time desynchronization has occured. I get to take the blame for it, but I also just fixed it so I guess it's a wash.

The problem should not recur!

Edit

Translation: When we failed over to our secondary datacenter because of Hurricane SUPERSTORM Sandy, we didn't set up time synchronization correctly so our servers got out of sync. Two submissions to different servers could thus get timestamps off by up to a minute or two.

share|improve this answer
6  
In english for the layperson? :-) –  Chimera Nov 21 '12 at 17:56
2  
seize FSMO roles, AD environment, PDC Emulator. What? –  Chimera Nov 21 '12 at 17:57
2  
    
@NullUserExceptionอ_อ thanks! –  Chimera Nov 21 '12 at 18:01
17  
We can't all just blindly upvote this and pretend we know what it says! This isn't /review! –  animuson Nov 21 '12 at 18:02
    
Oh, I thought this was the place to pretend to know what he's talking about and make disparaging comments toward everyone who doesn't. What sort of self-respecting person doesn't know what FSMO is LOL. –  TCPMAN.EXE Nov 21 '12 at 18:05
    
But what about the flux capacitor? –  Bart Nov 21 '12 at 18:18
    
Haha, sorry guys. @DavidFullerton broke it down wonderfully. –  Peter Grace Nov 22 '12 at 0:28
    
I don't believe you. It was this and you know it: images1.wikia.nocookie.net/__cb20101214205521/bttf/images/b/b6/… –  Ben Lee Nov 24 '12 at 8:18
add comment

This was caused by the same time sync issues as Eeek! Chat made the robot precognitive!, which also has an answer by Pete with an acronym-laden explanation.

share|improve this answer
add comment

Something bad happened to the NTP sources in the US over the weekend. You can see reports across the net, eg here. I'd wager this is something to do with it.

share|improve this answer
    
"The clocks should have been marked as insane" - nice –  Rawling Nov 21 '12 at 17:58
add comment

You must log in to answer this question.

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