On Thu, 11 Jun 2009, Stanislav Malyshev wrote:
> Bug #48247 appears to be not entirely fixed still, it still produces a torrent
> of warnings in certain configs (namely, take php.ini-production and edit it to
> enable error_log, don't touch anything else - I get 400K worth of warnings).
> Attached
On 16.06.2009, at 10:07, Derick Rethans wrote:
On Thu, 11 Jun 2009, Stanislav Malyshev wrote:
Bug #48247 appears to be not entirely fixed still, it still
produces a torrent
of warnings in certain configs (namely, take php.ini-production and
edit it to
enable error_log, don't touch anything
Hi!
So lets delay fixing this issue until 5.3.1? Of course it can be fixed
in HEAD right now :)
Delaying the fix would mean we release 5.3.0 that in mostly default
config has an infinite loop bug. Maybe we can at least have temp fix and
then when we have a proper one then remove it (or leave
hi,
On Tue, Jun 16, 2009 at 6:56 PM, Stanislav Malyshev wrote:
> Hi!
>
>> So lets delay fixing this issue until 5.3.1? Of course it can be fixed in
>> HEAD right now :)
>
> Delaying the fix would mean we release 5.3.0 that in mostly default config
> has an infinite loop bug. Maybe we can at least
Hi!
5.2 is likely to be released on Thursday, please, try to figure out a
solution before that or to convince Ilia to wait, thanks :)
Well, there is a patch I sent, which fixes the immediate problem, if
Ilia OKs it I can commit it any time. The comprehensive fix would take
some time though.
On 16.06.2009, at 18:56, Stanislav Malyshev wrote:
Hi!
So lets delay fixing this issue until 5.3.1? Of course it can be
fixed in HEAD right now :)
Delaying the fix would mean we release 5.3.0 that in mostly default
config has an infinite loop bug. Maybe we can at least have temp fix
an
Hi!
so if this issue is also in 5.2 .. i feel even less inclined to delay a
stable 5.3 release because of this issue. have we made it worse in our
attempts to fix it? the fact that this bug isnt fixed yet could mean
No, it was crash before, now it doesn't crash for me but produces 400K
of e
On 16.06.2009, at 20:53, Stanislav Malyshev wrote:
Hi!
so if this issue is also in 5.2 .. i feel even less inclined to
delay a stable 5.3 release because of this issue. have we made it
worse in our attempts to fix it? the fact that this bug isnt fixed
yet could mean
No, it was crash be
On Wed, Jun 17, 2009 at 12:01 AM, Lukas Kahwe Smith wrote:
> It seems only you and Derick have expressed an opinion.
> If no one else speaks up I would tend to leave as is and fix it in 5.3.1
> (and HEAD asap) and simply make sure that we put it in bold letters in the
> UPGRADING guide that you re
