Bug #75642 [Ver]: Wrap around behaviour for microseconds is not working

From: Date: Mon, 23 Apr 2018 14:21:33 +0000
Subject: Bug #75642 [Ver]: Wrap around behaviour for microseconds is not working
References: 1  Groups: php.bugs 
Request: Send a blank email to php-bugs+get-214843@lists.php.net to get a copy of this message
Edit report at https://bugs.php.net/bug.php?id=75642&edit=1 ID: 75642 Updated by: cmb@php.net Reported by: marcospassos dot com at gmail dot com Summary: Wrap around behaviour for microseconds is not working Status: Verified Type: Bug Package: Date/time related Operating System: OSX PHP Version: 7.2.0 -Assigned To: +Assigned To: derick Block user comment: N Private report: N New Comment: I've filed a respective ticket upstream[1]: <https://github.com/derickr/timelib/issues/35>. Previous Comments: ------------------------------------------------------------------------ [2018-04-23 09:16:32] requinix@php.net Related To: Bug #76252 ------------------------------------------------------------------------ [2018-03-09 15:06:04] requinix@php.net Microseconds are actually their own distinct integer. Off by one error. https://github.com/php/php-src/blob/PHP-7.2.0/ext/date/lib/tm2unixtime.c#L42 Additionally it's only able to over-/underflow the seconds by a change of 2. https://3v4l.org/4Ra66 ------------------------------------------------------------------------ [2018-03-09 12:06:12] cmb@php.net > pretty sure the sad float precision problem Apparently[1]. However, 2017-12-31 23:59:59.1000000 is wrong nonetheless. [1] <https://3v4l.org/e3utY> ------------------------------------------------------------------------ [2018-01-21 19:12:30] marcospassos dot com at gmail dot com Any update about this issue? ------------------------------------------------------------------------ [2017-12-06 22:26:26] spam2 at rhsoft dot net pretty sure the sad float precision problem which makes me wonder why it's called computer and not guesser ------------------------------------------------------------------------ The remainder of the comments for this report are too long. To view the rest of the comments, please view the bug report online at https://bugs.php.net/bug.php?id=75642 -- Edit this bug report at https://bugs.php.net/bug.php?id=75642&edit=1

« previous php.bugs (#214843) next »