@fanf but.. time never went back, a second lasted two seconds.
-
-
-
many leapsecond implementations go back a second to repeat 23:59:59 rather than stretching it
- 4 more replies
New conversation -
-
-
.
@Cloudflare Leap second issue was not a golang fault, IMHO, but also a lack of defenssive programming. From 6th ed. UNIX. Note <=, not ==pic.twitter.com/UJOo6Ljpah
-
I sometimes wrote > 0 in C even for uints, as explicit invariant/assert, but latterly compilers started whining.
- 1 more reply
New conversation -
-
-
@jgrahamc Thanks for the write up. What do you think about adding the new unit test to the blog post as well?Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
thanks for the postmortem, always an interesting read, and thanks for the transparency
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
one of the articles we shared on our newsletter
Really cool!Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
Isn't a DNS Server restart enough to fix this? Time shouldn't go back every time… :)
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
was there a code rewrite or infra chance since the last leap second 18 months ago?
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
out of interest, do you have engineers on-site in all PoPs?
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.