Re: [mythtv-users] mythfilldatabase: Ignoring unknown timestamp format: 20161231235960

On 12/18/2016 3:30 AM, Ian Campbell wrote:
>>        {
>>          "videoProperties": [
>>            "letterbox"
>>          ],
>>          "new": true,
>>          "md5": "mOC4USUaW5ASAWno3ii81A",
>>          "programID": "EP025790950001",
>>          "liveTapeDelay": "Live",
>>          "duration": 2100,
>>          "airDateTime": "2016-12-31T23:25:00Z"
>>        }
> Is this correct? A program running from 23:25 until midnight is 35
> minutes, which is 2100 seconds, but with the leap second should it not
> be 2101?

First, on testing, don't worry about "perl Makefile.pl".  Not sure why 
it's failing, but you probably can just run the tv_grab_sd_json from the 
new distribution... Makefile.PL doesn't change it.

Second, I don't think this will ever work.  The leap second is not 
something like a timezone.  It is simply mucking with the actual time, 
and I don't think you should expect the system to deal with it.  I ran 
some test scripts, and the Unix/PHP date functions don't take a leap 
second into account across 2017 New Years.

Third, I bet the official "2016-12-31 23:59:60"  wouldn't compute on 99% 
of the code running in the world.

Because of all the problems, I'm sure 99% of the world simply ignores it 
and you should too. :)  The master clocks will process the leap second 
and the next time the clock value trickles down to you (through various 
NTP servers), you'll be on the correct time. Your system is seldom 
"correct" anyway..... each time you check in with the NTP server the 
time is adjusted a bit.  This will be no different.

Robert






------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most 
engaging tech sites, SlashDot.org! http://sdm.link/slashdot