-
Notifications
You must be signed in to change notification settings - Fork 116
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Declaration of Carbon\Carbon::setTime($hour, $minute, $second = 0) should be compatible with DateTime::setTime($hour, $minute, $second = NULL, $microseconds = NULL) #914
Comments
Update Carbon library to latest version may solve this problem. |
Carbon::setTime($hour, $minute, $second = NULL) not compatible with http://php.net/manual/en/datetime.settime.php On line 681 of the includes/lib/Carbon.php the function setTime is missing the $microseconds = null parameter |
Any luck getting your PR committed? |
Negative it always seems to fail the continuous integration, for now I've
just manually made the edits that I needed
…On Tue, Nov 7, 2017 at 10:31 AM, Ahmed Khalil ***@***.***> wrote:
Any luck getting your PR committed?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#914 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/AXMXyd-N5Zpy1Dg1gHVWY5xj_QOZ4mBIks5s0KIJgaJpZM4MoKrh>
.
|
@Danny-Guzman I think the test |
I just switched from PHP 5.6 to 7.2 and found this warning...
The same issue also affects the Date Range Filter plugin you worked on. Any chance of a resolution? |
PHP 7.1 changes how Datetime handles microseconds, see http://php.net/manual/de/migration71.incompatible.php#migration71.incompatible.datetime-microseconds.
Looks like this also affects
DateTime::setTime()
which now has a$microseconds
parameter.The text was updated successfully, but these errors were encountered: