3 ms·
We were bitten by this once, and we ended up relying on TAI and then making leap second deviations _very_ clear to users. I never really got what the problem w
by Johnny_Brahms 11y ago
We were bitten by this once, and we ended up relying on TAI and then making leap second deviations _very_ clear to users.
I never really got what the problem was, but apparently someone had been careless about comparing times on some transaction which ended up giving a client a bad day.
This was some time ago, and if this stuff actually matters to you you probably know how to deal with it.