Last month we covered the 2015 leap second ahead of the insertion of a leap second at the very end of 2016. As stated previously, leap seconds can trigger poorly-tested code paths; leap second handling always unearths bugs and issues. This one was no exception!
Posted by Stephen Strowes on Monday, January 16th, 2017. You can follow me on twitter.
All content, including images, © Stephen D. Strowes, 2000–2016. Hosted by Digital Ocean.