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

On 12/19/2016 11:16 AM, Ian Campbell wrote:
> On Sun, 2016-12-18 at 14:43 -0600, Robert Eden wrote:
>> If Gracenote sent 2101 seconds and that was used to compute a stop
>> times, all stop times post leap second would be off as the system clock
>> was updated.  I think 2100 is the best answer as it only effects shows
>> that stop at exactly midnight.
> Minor nit: It appears to affect any show which crosses over midnight
> (or more accurately, a leap second), e.g. up thread I reported this
> series of shows:
>
> picking another random one with 5959 in it though:
>      <programme start="20161231170000 +0000" stop="20161231190000 +0000" channel="31786">
>      <programme start="20161231190000 +0000" stop="20170101005959 +0000" channel="31786">
>      <programme start="20170101010000 +0000" stop="20170101060000 +0000" channel="31786">
>      <programme start="20170101060000 +0000" stop="20170101080000 +0000" channel="31786">
>
> which has the blip between 20170101005959 and 20170101010000.
>
> But I don't think that invalidates the thrust of your argument.
>
It's interesting that your time APIs seem to be aware of the upcoming 
leap second.  I didn't test with perl DateTime, but I did try PHP... I 
expected both used the OS API and didn't seem to know about the leap second.

What OS are you using?

Robert


------------------------------------------------------------------------------
Developer Access Program for Intel Xeon Phi Processors
Access to Intel Xeon Phi processor-based developer platforms.
With one year of Intel Parallel Studio XE.
Training and support from Colfax.
Order your platform today.http://sdm.link/intel