6 ms·
Perhaps nitpicking, but this is because of a bug in the leap second implementation, not in the leap second per se.
by efutch 14y ago
Perhaps nitpicking, but this is because of a bug in the leap second implementation, not in the leap second per se.
- Uchikoma 14y agoI'd guess it happens by the concurrence of a lep second and a leap second implementation bug. The bug without leap seconds would also not lead to problems.