Rasmus Lerdorf wrote:
some other alternatives which was proposed in the past:
- Not a bug, proposed by Philip and others
- NFF/No Fault Found, proposed by RQuadling
honorable mentions:
- pebkac, doofus, and 'not our problem' from yawk
- SEP (Someone else's problem) from cjones
583:
hi Justin,
I'm totally for that, has been asked it for years.
Let see what other nicer status we need as wel :)
Cheers,
On Wed, Jan 25, 2012 at 12:11 AM, Justin Martin frozenf...@php.net wrote:
Hello,
With some frequency, I find bugs which are not bogus, so much as they are
reported based
On Wed, Jan 25, 2012 at 04:23, Pierre Joye pierre@gmail.com wrote:
hi Justin,
I'm totally for that, has been asked it for years.
Let see what other nicer status we need as wel :)
Cheers,
On Wed, Jan 25, 2012 at 12:11 AM, Justin Martin frozenf...@php.net wrote:
Hello,
With some
Hi Stas,
We've just found one more critical problem in 5.4.
Apache/PHP crashes in case of error on startup, when
display_startup_errors=1. It's probably related to new output API.
I afraid it may affect many php users.
#0 0x7ff4509cb471 in php_apache_sapi_header_handler
the main difference is php_sprintf
in 5.3 it calls OG(php_body_write) which points to php_default_output_func at
tha point.
in 5.4 it calls php_output_write, which writes output via SAPI.
On Wednesday, January 25, 2012 05:07:15 PM Dmitry Stogov wrote:
Hi Stas,
We've just found one more
On Wed, 25 Jan 2012 19:07:15 +0400, Dmitry Stogov wrote:
Hi Stas,
We've just found one more critical problem in 5.4.
Apache/PHP crashes in case of error on startup, when
display_startup_errors=1. It's probably related to new output API.
I afraid it may affect many php users.
...
In
Hi!
We've just found one more critical problem in 5.4.
Apache/PHP crashes in case of error on startup, when
display_startup_errors=1. It's probably related to new output API.
I afraid it may affect many php users.
OK, thanks. Looks like we'd be needing another RC then. Let's fix this
one
On Wed, 25 Jan 2012 09:13:43 -0800, Stas Malyshev wrote:
Hi!
We've just found one more critical problem in 5.4.
Apache/PHP crashes in case of error on startup, when
display_startup_errors=1. It's probably related to new output API.
I afraid it may affect many php users.
OK, thanks.
On Tue, 24 Jan 2012 20:33:10 +0100, David Soria Parra wrote:
I understand that it's useful, so you suggested having a mail for each
commit instead of each push. I prefer mails per push as they are the
only documentation of who pushed what. In case someone pulls from a
person that doesn't
On 1/24/12 5:47 PM, Ferenc Kovacs wrote:
On Wed, Jan 25, 2012 at 12:11 AM, Justin Martinfrozenf...@php.net wrote:
Hello,
With some frequency, I find bugs which are not bogus, so much as they
are reported based on a misunderstanding. Usually this happens for
documentation problems, where
Hi,
I currently work on a daemon implemented in PHP and as such, I want to keep
all configurations in place while the php binary can be used by other cli
scripts with the default /etc/php.ini file. I could recompile PHP and add a
new folder to the folder which is scanned for php.ini files. A
Hi Internals,
we are a few weeks into the git migration, so I want to give you a short
status update.
- web/ is completly migrated. all php websites are updating from
the git repositories now. Checkout http://git.php.net/
- We support SSH keys now. Go to
On 26/01/12 00:22, Robert Eisele wrote:
My specific problem could be tackled in two ways:
- Scan . every time cli is called for a php.ini file or
- Try to make argv interpretation more intelligent and parse/merge shebang
parameters.
There are |.user.ini files, but only for CGI/FastCGI
I've never gotten -d in shebang to work properly, I'd love to see that working.
-Original Message-
From: Ángel González [mailto:keis...@gmail.com]
Sent: Wednesday, January 25, 2012 6:00 PM
To: Robert Eisele
Cc: PHP internals
Subject: Re: [PHP-DEV] Shebang parsing
On 26/01/12 00:22,
it has a length limit, if I remember correctly it is some reall short value
on linux.
it seems to be 127 character:
http://www.in-ulm.de/~mascheck/various/shebang/
2012/1/26 Clint M Priest cpri...@zerocue.com
I've never gotten -d in shebang to work properly, I'd love to see that
working.
--
vrana has raise a good point in a potentially dangerous behavior with ini_set()
in https://bugs.php.net/bug.php?id=60668.
Here is my proposed patch. Feedback is appreciated. Thanks!
Kiyoto Tamura
diff --git a/Zend/zend_ini.c b/Zend/zend_ini.c
index a7ec5d7..89b1287 100644
--- a/Zend/zend_ini.c
Hello,
On Wed, Jan 25, 2012 at 5:43 PM, Kiyoto Tamura m...@ktamura.com wrote:
vrana has raise a good point in a potentially dangerous behavior with
ini_set() in https://bugs.php.net/bug.php?id=60668.
Here is my proposed patch. Feedback is appreciated. Thanks!
Kiyoto Tamura
diff --git
Thanks for the pointers. While I agree with you that application developers
must be cognizant of input sanitization, I am not sure what's the value of
allowing CR-LF in the user agent value. Said another way, if the user agent
contains CR-LF, it was most definitely not meant to be there. Can
Also, I am not sure if php_trim is what we want here. It looks like vrana's
initial proposal was to discard everything after CR-LF. This is different from
trimming CR/LF/whitespace at the end of the string.
I suppose that's a less important issue. I am mainly curious about your opinion
as to
Hello,
On Wed, Jan 25, 2012 at 9:32 PM, Kiyoto Tamura m...@ktamura.com wrote:
Also, I am not sure if php_trim is what we want here. It looks like vrana's
initial proposal was to discard everything after CR-LF. This is different
from trimming CR/LF/whitespace at the end of the string.
Ah I
Thanks for elaborating on the BC break (I googled it to no avail). I guess
such a change (discarding everything after CR-LF) would break the code using BC
breaks.
Either way, at least I am fully aware of how ini_set behaves ;)
On Jan 25, 2012, at 9:25 PM, Chris Stockton wrote:
Hello,
On
21 matches
Mail list logo
