Ilia Alshanetsky wrote:
The second release candidate of 5.2.12 was just released for testing
FWIW, I'm getting a
./configure: 91396: Syntax error: fi unexpected
when trying to run the configure script (on Ubuntu 8.04) like so:
./configure --enable-mbstring --with-mysql=/usr/local/mysql
I just spent about an hour debugging some XML-RPC communication only to
find that the problem was not in my code but in PHP 5.2.2RC2 apparently.
I'm using PEAR::XML_RPC (current version) which seems to rely on
$HTTP_RAW_POST_DATA. And even though I had always_populate_raw_post_data
= Off in my
I believe this is a bug in PHP 5.2.2. I've tried to report this for PHP
5.2.2RC2 but apparently wasn't making myself clear or wasn't following
the proper procedures ...
Anyway, as I wrote before[1], raw POST data isn't making it through in
PHP 5.2.2 which results in XML-RPC communications to
Ilia Alshanetsky wrote:
Is your always_populate_raw_post_data enabled?
Yes:
; Always populate the $HTTP_RAW_POST_DATA variable.
always_populate_raw_post_data = On
As I already said: On or Off doesn't seem to make a difference.
Also, have you tried
accessing the data from php://input ?
I
Ilia Alshanetsky wrote:
Also, have you tried accessing the data from php://input ?
Okay, that appears to work. Using this script as the receive.php:
?php
echo (file_get_contents(php://input));
?
I now get
---GOT---
HTTP/1.1 200 OK
Date: Sat, 05 May 2007 08:01:49 GMT
Server: Apache/1.3.37
David Coallier wrote:
Anyone has an answer/tests to that bug* so we can stop this discussion ? :)
The bug has apparently been fixed in CVS. Haven't had a chance to test
it, but will do as soon as possible.
Now the question is: When can we expect an update? I see people talking
about what
Ilia Alshanetsky wrote:
The bug has apparently been fixed in CVS. Haven't had a chance to test
it, but will do as soon as possible.
Please let me know how it works out.
I've tested php5.2-200705071830.tar.gz from snaps.php.net and the bug
seems to be fixed. Thanks.
One interesting feature
Quoting Johannes Schlüter johan...@schlueters.de:
I have the impression that very few people actually test these. When
creating an RC we inform the primary testers as well as qa and
internals list members. From there I get one or two responses in
general.
What happens to the reports that make
Quoting Ferenc Kovacs tyr...@gmail.com:
On Wed, Aug 24, 2011 at 1:59 PM, Ryan McCue li...@rotorised.com wrote:
Ferenc Kovacs wrote:
the aggregated report summaries are available at
http://qa.php.net/reports/ thanks to Oliver Doucet who make this
happen.
Which, incidentally, doesn't appear
Quoting Ferenc Kovacs tyr...@gmail.com:
There is only three failing tests left on the debian slaves:
For 5.3
ext/phar/tests/phar_oo_005.phpt.Phar and RecursiveDirectoryIterator 0.01 20
ext/spl/tests/bug60082.phpt.Bug #60082 (100% CPU / when using references
with ArrayObject($ref))
FWIW, the
I've notice, back in PHP 5.4.0 beta 2, that this test was failing:
Bug #48555 (ImageFTBBox() differs from previous versions for texts with new
lines) [ext/gd/tests/bug48555.phpt]
So I went to https://bugs.php.net/bug.php?id=48555 and left a comment.
The same test still fails in 5.4.0RC1 and
Stas Malyshev wrote:
And if we had rule of no failing tests, we'd have no
releases for years now, because nobody is fixing those tests and bugs
behind them.
I was about to suggest that maybe PHP should have a rule: no release with
failing tests.
What's the point of a test that fails (or
a friendly reminder that there are people
out there that are still deploying applications that will have to run on
PHP 4 and a plea for not neglecting that part of your user base.
Thanks for your attention.
regards,
Dirk Haun
(Maintainer, Geeklog 1.x)
[1] We're one of the projects on the PhP4zy list
Am 13.07.2010 um 17:12 Uhr schrieb Ferenc Kovacs:
it would be an interesting to check how many bugs were first marked as
bogus then re-opened and fixed.
I've been wondering for a while now if much of the emotional reaction to bugs
being closed as bogus is due to that very word. I mean, the
14 matches
Mail list logo
