On Mon, 22 Aug 2011 08:10:28 +0200, ka...@php.net (Kalle Sommer Nielsen)
wrote:
>> After upgrading to php 5.3.7, whenever I use is_a($object, 'ClassName');
>> the autoloader of classes is now called.
>>
>> This did not happen in earlier versions of php 5.3 that I used before.
>> But I cannot find
Hi
2011/8/22 Mads Lie Jensen :
> Hi.
>
> After upgrading to php 5.3.7, whenever I use is_a($object, 'ClassName');
> the autoloader of classes is now called.
>
> This did not happen in earlier versions of php 5.3 that I used before.
> But I cannot find any mention of it anywhere, no open bugs for
Hi.
After upgrading to php 5.3.7, whenever I use is_a($object, 'ClassName');
the autoloader of classes is now called.
This did not happen in earlier versions of php 5.3 that I used before.
But I cannot find any mention of it anywhere, no open bugs for it, and
nothing in the changelogs.
Is it a
On Mon, Aug 22, 2011 at 1:49 AM, David Muir wrote:
> Why not provide a userland fallback?
>
> eg: /IGBinary/unserialize()
>
> It could unserialize the string, albeit slowly, but still give you
> access to the data without needing the extension. At least that way you
> have something rather than n
On 08/19/2011 10:54 PM, Ferenc Kovacs wrote:
> On Fri, Aug 19, 2011 at 2:47 PM, Arpad Ray wrote:
>> On Fri, Aug 19, 2011 at 1:40 PM, Ferenc Kovacs wrote:
>>> On Fri, Aug 19, 2011 at 2:31 PM, Arpad Ray wrote:
On Fri, Aug 19, 2011 at 1:04 PM, Ferenc Kovacs wrote:
> the downside would be
On Sun, Aug 21, 2011 at 8:55 PM, Reindl Harald wrote:
>> be the server or the libmysql
>
> we are speaking about mysqlnd, libmysql is not involved
> the problem is taht something for libmysql was fixed and breaking mysqlnd
It was about giving examples where similar issues happened in the
past, no
> be the server or the libmysql
we are speaking about mysqlnd, libmysql is not involved
the problem is taht something for libmysql was fixed and breaking mysqlnd
please look again at https://bugs.php.net/bug.php?id=55283
there is a comment "Changing mysqli to make libmysql happy will cause leaks
That's not why I said.
There could have a bug in the server making the actual valid fix not
working with some versions. It happened already a lot in the past (be
the server or the libmysql).
On Sun, Aug 21, 2011 at 8:46 PM, Reindl Harald wrote:
> hardly to understand because the mysql-server is
hardly to understand because the mysql-server is unchanged
mysql 5.5.15 and before 5.3.7 there was no problem for
over a year - so if the only changed component is PHP 5.3.7
how should the problem be not PHP?
Am 21.08.2011 20:30, schrieb Pierre Joye:
> hi,
>
> I shortly discussed this issue with
hi,
I shortly discussed this issue with Ulf. As far I can tell it is not
certain that this bug is in php itself but on the server side. It
means that the fix applied in 5.3.7 actually works with server
versions but not other.
However we can't take a decision without their agreement (no revert if
both have nothing to do with the php core. Please stay on topic thanks.
Thanks,
On Sun, Aug 21, 2011 at 5:31 PM, Reindl Harald wrote:
> if anybody is using "php-pecl-memtrack.so" and relies on suhoosin
> to disable dangerous function per directory he should not trust
> the output of phpinfo() an
if anybody is using "php-pecl-memtrack.so" and relies on suhoosin
to disable dangerous function per directory he should not trust
the output of phpinfo() and disable "memtrack"!
http://pecl.php.net/bugs/bug.php?id=23826
signature.asc
Description: OpenPGP digital signature
Am 21.08.2011 16:21, schrieb Daniel Convissor:
> Hi Reindl:
>
> On Sun, Aug 21, 2011 at 03:08:09PM +0200, Reindl Harald wrote:
>> This is my try to help badly prevent broken releases like
>> 5.3.7 in the future, 54 failing tests are way too much and
>> the XFAILED should be removed until they are
Hi Again Reindl:
On Sun, Aug 21, 2011 at 10:21:40AM -0400, Daniel Convissor wrote:
> On Sun, Aug 21, 2011 at 03:08:09PM +0200, Reindl Harald wrote:
>
> > FAIL DateTime::diff() days -- spring type2 type2
> > [ext/date/tests/DateTime_days-spring-type2-type2.phpt]
> > FAIL DateTime::diff() days -- s
Hi Reindl:
On Sun, Aug 21, 2011 at 03:08:09PM +0200, Reindl Harald wrote:
> This is my try to help badly prevent broken releases like
> 5.3.7 in the future, 54 failing tests are way too much and
> the XFAILED should be removed until they are working
XFAIL's should stay, in my opinion. Their resu
Am 21.08.2011 15:21, schrieb Pierre Joye:
> hi,
>
> The question is more about whether this bug was present before as
> well. If yes, I'd to wait to make sure we get 5.3.8 out on Tuesday
> without any other change but the crypt's fix
as said it was broken with 5.3.7
what about release 5.3.8 w
hi
it was surely not present in mysqlnd before because we are running a bundle
of servers which using the same ssl-certs for php and mysql over WAN and all
of them started running in timeot/mysql server gone away directly
after update to PHP 5.3.7 (we are speaking about cronjobs every 5 minutes)
hi,
The question is more about whether this bug was present before as
well. If yes, I'd to wait to make sure we get 5.3.8 out on Tuesday
without any other change but the crypt's fix.
Cheers,
On Sun, Aug 21, 2011 at 3:08 PM, Reindl Harald wrote:
> This is my try to help badly prevent broken rel
This is my try to help badly prevent broken releases like
5.3.7 in the future, 54 failing tests are way too much and
the XFAILED should be removed until they are working
the crypt()-bug which is the reason for 5.3.8 this week is fixed
in this build with the patch included on fedora-buildserver
Te
hi,
On Sun, Aug 21, 2011 at 3:57 AM, Adam Harvey wrote:
> Depending on the timeframe for 5.3.8, should we be pulling 5.3.7 from the
> front page (or posting additional news) so users don't inadvertently end up
> with crypt() issues?
We should, anyone with web karma could add a note on www?
5.3
20 matches
Mail list logo
