Cloudflare wrote up the postmortem for their leap second outage up and it was this exact problem! https://blog.cloudflare.com/how-and-why-the-leap-second-affected-cloudflare-dns/ …
Another leap second, another slew of outages. Handling time correctly is hard! https://github.com/golang/go/issues/12914 …pic.twitter.com/Fwz2Xtpzkd
-
-
- 1 more reply
New conversation -
-
-
Erlang solved this in OTP 18 by adding 5 time methods w/ configurable skew strategy (discontinuity or smeared), including monotonic
-
Python did the same with PEP 418, but folks still need to learn when they should use time.monotonic rather than time.time.
- 2 more replies
New conversation -
-
-
Wow, that comment saying (paraphrased) "golang is only supported on systems that use leap smearing"!
-
Go was quite literally designed by the New Jersey people from Worse Is Better.
- 1 more reply
New conversation -
-
-
2017, making people aware of what a monotonic clock is, and how theirs isn't
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
Time is not as simple as it seems ;)
-
New conversation -
-
-
the highlighted bit in the first image is just breathtaking. the efficient markets hypothesis of software.
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.