{'fraction_non_alphanumeric': 0.035493827160493825, 'fraction_numerical': 0.0, 'mean_word_length': 5.0092592592592595, 'pattern_counts': {'":': 0, '<': 0, '<?xml version=': 0, '>': 0, 'https://': 0, 'lorem ipsum': 0, 'www.': 0, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 0, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
Leap Second support in computers

The seconds-in-epoch method of representing current time in computers presents problems when required to (a) represent UTC, (b) be monotonic and (c) have sub-second accuracy, as these are contradictory requirements in the presence of Leap Seconds. We analyze various proposed solutions to this conundrum, for both operating systems and NTP. (What good is microsecond-level clock synchronization if the clock can be off by a full second?) We then propose a general solution: TAI-based system time, with conversion to UTC by comparing to a TAI-based threshold and then subtracting the appropriate Leap Second Offset.