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
DateTimeZone::getTransitions doesn't accept optional parameters #2479
Comments
Our application also encounters a similar error due to this issue. |
Getting the exact same error with the following code:
|
I have the same issue |
Same issue with my DateTime extension: |
We're also affected, a workaround is in place for us but looking forward to the fix becoming available. |
I've started working on this. |
@jackdied I already have a diff up internally for this. Internal Diff: D1658643 |
I am waiting for the |
Ah, I hadn't seen that. I started a similar in D5620779. Keep an eye on that "int timestamp". I didn't get far enough in the task to chase it down but signed int time_t's are an accident waiting to happen. edit: /differential/diff/5620779/, just a preview so apparently not in the "D" namespace. |
DateTime is now HNI (Yay!!) I have a new internal diff since I didn't want to go through the rebase process with the HNI conversion D1724025 |
Since PHP 5.3.0, DateTimeZone::getTransitions has been accepting two optional integer parameters: $timestamp_begin and $timestamp_end: http://www.php.net/manual/en/datetimezone.gettransitions.php
HHVM doesn't seem to support it, given that running this on hphpd gives a warning:
The text was updated successfully, but these errors were encountered: