-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Le 27/02/2015 09:06, Sebastian Bergmann a écrit :
> While working on PHPUnit today I noticed one test of its own test
> suite failing on PHP 5.6.6 that passes on PHP 5.6.5. The details
> of this can be found at
>
> https://github.com/sebastianbergman
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Le 17/03/2015 14:12, Jan Schneider a écrit :
> Hello,
>
> now that RFCing has settled down a bit, and things should get back
> to more development and less politics, can someone please take a
> look at this regression: https://bugs.php.net/bug.php?id=
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Le 26/03/2015 16:21, Xinchen Hui a écrit :
> Hey Internal:
>
> there is one confused behavior with disable_functions:
>
> $ sapi/cli/php -n -d disable_functions=strlen -r
> 'var_dump(function_exists("strlen"));
> var_dump(is_callable("strlen"));' b
Le 15/04/2015 07:08, Xinchen Hui a écrit :
> Hey：
>
> Sent from my iPhone
>
>> On Apr 15, 2015, at 10:21 AM, Pierre Joye wrote:
>>
>> hi,
>>
>> We tried that many times but we fail to handle the version of bundled
>> extensions.
>>
>> Along with some installer work and other integration (project
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Le 15/04/2015 11:47, Pierre Joye a écrit :
> On Apr 15, 2015 4:12 PM, "Remi Collet"
> wrote: , I still +1 on this
>>>
>>
>> I'm mostly +1 on this proposal.
>>
>> Of course extension (like o
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
Current workflow described in
https://wiki.php.net/vcs/gitworkflow#merge_a_pull_request
Problem, git history only give info about a "merge"
Ex, after merging 1278:
http://git.php.net/?p=php-src.git;a=commit;h=eef762d576e7744d6e0c8d6a3f997fe911
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Le 29/05/2015 09:18, Kalle Sommer Nielsen a écrit :
> Commit:7dcfdbbee431c93c52605e1df323d18e0c6088e9 Author:
> Kalle Sommer Nielsen Fri, 29 May 2015
> 09:18:36 +0200 Parents: 0e079f9358be65c4cae5dd938b4924abec0564ac
> Branches: master
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Le 25/06/2015 16:41, Jan Ehrhardt a écrit :
> Kalle Sommer Nielsen in php.internals (Thu, 25 Jun 2015 16:06:15
> +0200):
>> This release fixes about 25 bugs reported since the first alpha
>> and it implements the Throwable interface with changes to the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
See https://bugs.php.net/bug.php?id=70112
As this a very small self-contained change,
I don't think it needs a RFE.
Feedback welcome
Remi.
-BEGIN PGP SIGNATURE-
Version: GnuPG v2
Comment: Using GnuPG with Thunderbird - http://www.enigmail.
Le 22/07/2015 20:57, Marco Pivetta a écrit :
> On 22 July 2015 at 19:49, Sara Golemon <mailto:poll...@php.net>> wrote:
>
> On Wed, Jul 22, 2015 at 4:55 AM, Remi Collet
> mailto:r...@fedoraproject.org>> wrote:
>> See https://bugs.php.net/bug.php?id=70112
>>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Le 24/07/2015 02:11, Hannes Magnusson a écrit :
> On Wed, Jul 22, 2015 at 4:55 AM, Remi Collet
> wrote:
>> -BEGIN PGP SIGNED MESSAGE- Hash: SHA1
>>
>> See https://bugs.php.net/bug.php?id=70112
>>
>>
&g
Hi,
Using "crypt" function is a mess
(perhaps one of the reason for password_hash)
This proposal provides more bindings:
* crypt_gensalt($salt, $count)
* crypt_preferred_method()
* crypt_checksalt($salt)
And more Algo
* scrypt
* yescrypt
* gost-yescrypt
These were already usable but very ha
Le 13/09/2024 à 09:57, Ayesh Karunaratne a écrit :
Assuming the intended use case is compatibility with `/etc/shadow` or
something similar, would it not make sense to add these algos to
`password_hash` function, and not add new functions?
Yes this another goal (later)
For now, these are provi
Le 13/09/2024 à 12:33, Christoph M. Becker a écrit :
However, Windows support might not be that important anyway,
So for now, my plans are:
- Maintain the xpass extension for PHP 8.x
New version 1.1.0 have the additional functions/macros
- Wait for user feedback/comments
- Open a RFC (afte
Le 26/12/2011 09:29, Stanislav Malyshev a écrit :
> stas Mon, 26 Dec 2011 08:29:11 +
>
> Revision: http://svn.php.net/viewvc?view=revision&revision=321406
ZTS build is broken (snapshot 201112261030)
Please see trivial attached patch
Regards,
Remi.
diff -
With 321411 applied
(gdb) run -n -m
Starting program: /dev/shm/php5.4-201112261030/build-zts/sapi/cli/php -n -m
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib64/libthread_db.so.1".
[PHP Modules]
bz2
calendar
Core
... ...
zlib
[Zend Modules]
Program received
Le 26/12/2011 14:09, Pierre Joye a écrit :
> Attached patch should fix this problem but I'm not sure if we have to
> do it in RINIT instead. The handler is set to NULL on dtor, so it
> could be enough already to do it once in MINIT.
At least, it fix the build/run issue.
Thanks.
--
PHP Internals -
Hi,
I'm working on PHP 5.4 as a fedora 17 feature.
https://fedoraproject.org/wiki/Features/Php54
Mainly, I test all available extension (~40) compatibility and try to
fix, when needed, and report bug upstream. (mostly done)
But I encounter a segfault with ice-php.
(gdb) bt
#0 _zend_mm_free_int
Le 29/12/2011 12:15, Pierre Joye a écrit :
> Does it happen only with the ice extension?
Yes.
> If yes I would suggest to contact the authors, which are in no way
> involved in php.net for this extension.
Yes, I understand.
Remi.
--
PHP Internals - PHP Runtime Development Mailing List
To unsub
Hi,
Can someone have a look to this annoying bug ?
I have try to move tsmr_startup to pre_config hook, but with no success.
I don't see any change in sapi/apache2handler which explain this issue
(no issue with 5.3.x, so must look somewhere else)
I really like to see ZTS available for apache use
Le 04/01/2012 10:05, Laruence a écrit :
> After I test, the patch is okey, so I commited it,
Thanks for the patch, works well.
Only a autoload bug with APC in ZTS, but this is another issue.
Remi
P.S. APC bug https://bugs.php.net/60658
--
PHP Internals - PHP Runtime Development Mailing List
Hi,
On http://snaps.php.net/
Lastest is php5.4-201201041830
Is something broken ?
Best regards,
Remi.
P.S. and FYI, php 5.4.0 will be in fedora 17
(RC5 should be in rawhide next week)
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
I fill a bug : https://bugs.php.net/bug.php?id=60748
(trivial patch proposed, shouldn't break anything)
Just a notice, there is no mysqlnd component in bug tracker...
(or I was unable to find it...)
Remi.
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www
Le 15/01/2012 00:12, Johannes Schlüter a écrit :
> In what case do you notice that? - ext/mysql, mysqli and PDO_mysql
> should override that. Only case I can see would be some mysqlnd plugin
> overriding the host.
You're right, this patch is an old one, before bug #60155 was fixed (in
r318696), a
Le 16/01/2012 18:39, Ulf Wendel a écrit :
> Am 16.01.2012 11:19, schrieb Remi Collet:
>> P.S. well, don't know if having such a hardcoded path is a good idea...
>
> mysqlnd is a libmysql drop-in replacement. Guess what libmysql does... -
> do "strings libmysqlclien
Le 03/02/2012 09:34, David Soria Parra a écrit :
> Hi internals
>
> We like to announce the 7th Release Candidate of PHP 5.4.0.
> We fixed some critical bugs in the PHP 5.4.0 codebase. Therefore we
> release another RC. Hopefully the last one before the final.
Hi internals
This version comes wit
Hi,
As PHP (co)maintainer in Fedora, I sometime need to access security bugs
which are private.
Ex: https://bugs.php.net/bug.php?id=55500
Can I be granted for such access ?
Regards,
Remi.
P.S. I already have an SVN account : remi
--
PHP Internals - PHP Runtime Development Mailing List
To un
Le 05/03/2012 17:44, Remi Collet a écrit :
> Perhaps, the new result is the right one... but I don't find any other
> tool to check it...
Using a simple C program (linked against libmash)
Hash: fdb9019a79c33a95677e2097abae91eb0de00b3054bb5c39
So the result from php <= 5.3.10 s
Please review https://bugs.php.net/bug.php?id=61291
And attached patch
Without the patch
37 PASSED TESTS
0 SKIPPED TESTS
2 FAILED TESTS:
mhash_001.phpt
mhash_003.phpt
With the patch
34 PASSED TESTS
0 SKIPPED TESTS
5 FAILED TESTS:
hash_copy_001.phpt
hash_file_basic1.phpt
hash_hmac_basic.phpt
h
Le 08/03/2012 09:03, Michael Wallner a écrit :
> On Mon, 05 Mar 2012 17:52:52 +0100, Remi Collet wrote:
>
>>
>> Using a simple C program (linked against libmash)
>>
>> Hash: fdb9019a79c33a95677e2097abae91eb0de00b3054bb5c39
>>
>> So the result from php <
Le 01/07/2012 00:59, Stas Malyshev a écrit :
> Hi!
>
> I see that there were significant changes committed to JSON extension in
> 5.3 and 5.4 recently.
Another minor documentation problem:
Last pecl version on json extension, released in 2006 was 1.2.1
Version included in 5.3 and 5.4 still rep
Can you confirm me when the public annoucement for final 5.4.6 will be
published ? (time)
I notice that http://windows.php.net/download/#php-5.4 already provides
5.4.6 when it is not announced...
I'm waiting for official announcement to publish some fresh RPM and push
update to Fedora.
Regards,
Hi,
I recently noticed that on http://www.php.net/downloads.php,
"Redhat/CentOS Binaries" link to a third party repository [1].
First, this could be confused for users, as this is not a Red Hat or
CentOS official repository.
Why PHP project (seems to) recommend the use of a third party repositor
Le 15/09/2012 10:58, Ferenc Kovacs a écrit :
> http://git.php.net/?p=web/php.git;a=commit;h=6d85653df2e1cb2c97003f0c42000f2129f976e1
> It seems somebody mailed the webmaster list and Hannes added them to
> that page.
> They are there because they provided up-to-date packages for redhat/centos.
> Y
Calling a not defined constructor produce an error in PHP 5.3.0 alpha2
(200809070630 snapshot) when it work in php <= 5.2.6 calling the parent one.
Ok using constructor with class name is a compatibility behaviour and
using __construct don't have this issue. But this regression could
introduce bre
Le 22/03/2009 06:15, Eric Stewart a écrit :
> Here is a link to the patches for review:
> http://www.ericstewart.org/public/20090322.inis-patch.zip
>
Just a note about php.ini-production (from RC1 tarball)
Line 581 should be a comment, I think :
http://www.php.net/manual/en/errorfunc.configurat
Le 02/10/2013 20:41, Jakub Zelenka a écrit :
> Hi,
>
> I was wondering why stream API has been changed in this commit:
>
> https://github.com/php/php-src/commit/92d27ccb0574f901a107409a7fec92888fa2b82f
>
> Basically all char pointers have been constified. The thing is that this
> commit leads to
Le 02/10/2013 20:41, Jakub Zelenka a écrit :
> Hi,
>
> I was wondering why stream API has been changed in this commit:
>
> https://github.com/php/php-src/commit/92d27ccb0574f901a107409a7fec92888fa2b82f
>
> Basically all char pointers have been constified. The thing is that this
> commit leads to
Le 17/07/2014 06:01, Laruence a écrit :
> $this->_prototype = unserialize(sprintf('O:%d:"%s":0:{}',
> strlen($this->name), $this->name));
>I am not sure now. should this usage be supported?
In think unserialize is an horrible hack which should have never be used.
This is descri
Notice,
All Internal classes, implementing Countable still doesn't accept this
optional parameter.
Ex:
Method [ public method count ] {
- Parameters [0] {
}
Indeed, all Spl classes still use zend_parse_parameters_none().
This work, because count($a) doesn't use th
Notice,
All Internal classes, implementing Countable still doesn't accept this
optional parameter.
Ex:
Method [ public method count ] {
- Parameters [0] {
}
Indeed, all Spl classes still use zend_parse_parameters_none().
This work, because count($a) doesn't use th
Le 23/07/2014 10:26, Remi Collet a écrit :
> Both solution "should" fix this:
> - adding the count_elements handler
> - accepting the optional mode
Both works.
> But, Reflection still not correct, and count($a) still raise the
IT is ok (sorry for the noise, tested wi
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Le 18/08/2014 08:10, Laruence a écrit :
> Hey:
>
> There are some PRs for supports of PowerPC64
>
> https://github.com/php/php-src/pull/734
> https://github.com/php/php-src/pull/735
> https://github.com/php/php-src/pull/736
> https://github.com/ph
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Le 18/08/2014 11:21, Stas Malyshev a écrit :
> BTW, it'd be nice to figure out why we have 6 fails there :)
I already spent a lot of time fixing various non-intel failed tests...
3 related to date can be ignored (because of fedora / red hat
system-tz
Le 17/08/2014 11:25, Ferenc Kovacs a écrit :
> Hi,
>
> I'm planning to release 5.6.0 from RC4 if nothing serious comes up,
> so this is just a heads-up: if you think that there is some fix,
> which should make into the 5.6.0 final (which isn't in RC4) or if
> you think that there is some blocker i
For now:
#define STR_REALLOC(ptr, size) \
ptr = (char *) erealloc(ptr, size);
Dealing with https://github.com/phalcon/cphalcon/pull/2772
I switch from realloc to str_realloc.
But this is not portable (str_realloc is 5.6+ only)
STR_REALLOC should be better, as portable,
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Running a test build of 5.4.33RC1.
Testing the fix for the SCRIPT_NAME issue
1. SetHandler Configuration
SetHandler "proxy:fcgi://127.0.0.1:9003"
URL = /info.php/a/b?q=a
SCRIPT_NAME = /info.php
=> OK
2. ProxyPass Configuration
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Le 05/09/2014 14:54, Philip Hofstetter a écrit :
> Applying the patch fpm_main-script_name-v2.patch proposed on
> https://bugs.php.net/bug.php?id=65641 fixes the issue for me.
This patch doesn't check for tflag, which seems usefull...
Another try
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Le 05/09/2014 15:52, David Zuelke a écrit :
> People should simply use the SetHandler approach instead.
I agree, see https://bugzilla.redhat.com/1136290
But some people may want to use ProxyPass (ex, to redirect to another
server, with no PHP script
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Le 09/09/2014 07:54, Stas Malyshev a écrit :
> Hi!
>
> So what is the resolution for this? Should we roll back the fix,
> implement the new one and have one more RC, do something else?
>
Sorry, it seems I have miss your question :(
As David Zuelke
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Le 11/09/2014 09:16, Remi Collet a écrit :
> Le 09/09/2014 07:54, Stas Malyshev a écrit : The big issue I see,
> is the news entry:
>
> . Fixed #65641 (PHP-FPM incorrectly defines the SCRIPT_NAME
> variable when using Apache). (David
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Le 11/09/2014 09:19, Remi Collet a écrit :
> Le 11/09/2014 09:16, Remi Collet a écrit :
>> Le 09/09/2014 07:54, Stas Malyshev a écrit : The big issue I
>> see, is the news entry:
>
>> . Fixed #65641 (PHP-FPM incorrectly
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Le 12/09/2014 10:07, Julien Pauli a écrit :
> Hi!
>
> Our RC1 of PHP 5.6.1 was just released today.
Hi.
More QA/CI is always a good thing!
Fedora have a new project named Koschei.
See
http://blog.famillecollet.com/post/2014/08/12/Koschei-continuo
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Le 18/09/2014 11:08, marius adrian popa a écrit :
> Maybe is time to vote and implement it in php 7 with a pull request
> for each sapi
>
> https://wiki.php.net/rfc/removal_of_dead_sapis
AFAIK, litespeed is not dead
It have be recently updated to lat
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Le 19/09/2014 17:30, Daniel Lowrey a écrit :
> In an effort to fix a very old (seven years old) DoS vulnerability
> involving encrypted streams I created a regression where feof()
> notifications on encrypted sockets are broken. This is present in
>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Le 19/09/2014 18:25, Daniel Lowrey a écrit :
>>> In an effort to fix a very old (seven years old) DoS
>>> vulnerability involving encrypted streams I created a
>>> regression where feof() notifications on encrypted sockets are
>>> broken. This is prese
Hi,
Sorry to have not detect this problem at RFC time, but the new hardcoded
cipher list, cause some trouble in Fedora.
See: https://bugs.php.net/68074
http://fedoraproject.org/wiki/Changes/CryptoPolicy
https://fedoraproject.org/wiki/User:Nmav/CryptoPolicies
https://wiki.php.net/rfc/improved-tls-
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
Sorry to have not detect this problem at RFC time, but the new hardcoded
cipher list, cause some trouble in Fedora.
See: https://bugs.php.net/68074
http://fedoraproject.org/wiki/Changes/CryptoPolicy
https://fedoraproject.org/wiki/User:Nmav/Crypto
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Le 24/09/2014 09:33, Ferenc Kovacs a écrit :
> We could have used the same NEWS entry from 5.6 I suppose: . Fixed
> bug #67606 (revised fix 67541, broke mod_fastcgi BC). (David
> Zuelke)
>
I fixed NEWS in 5.4 / 5.5 "before" the release (5.4.33 / 5.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Le 25/09/2014 09:00, Stas Malyshev a écrit :
> Hi!
Hi,
>> After a quick check
Too quick, I miss 84a4041 ;)
>> 6569db8 and 32be79d are in 5.4.33 / 5.5.17 / 5.6.1RC1 f86b219
>> and 3728449 are in 5.6.1RC1 only
>
> So, for 5.4 should we revert 6569db
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Le 26/09/2014 13:29, Florian Margaine a écrit :
> Hi internals,
>
> The question is in the title :-)
>
> As far as I know, most projects follow this convention: develop on
> the master branch, then backport the fixes/features to older
> versions.
>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Le 30/09/2014 05:06, guilhermebla...@gmail.com a écrit :
> Hi,
>
> Here is a new RFC: https://wiki.php.net/rfc/sync
Isn't this extension a bit "young" to join php core ?
Remi.
>
> Thoughts appreciated.
>
> Cheers,
>
-BEGIN PGP SIGNATURE
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
See https://bugs.php.net/63595
Short, changing gmp memory allocator can cause segfaults in various
case where gnutls is used and initialized "before" gmp.
- - php + gmp + curl => segfaults
- - apache + mod_php + mod_gnutls + gmp => segfaults
-
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Le 10/10/2014 12:57, Andrea Faulds a écrit :
>
>> On 10 Oct 2014, at 09:39, Remi Collet
>> wrote:
>>
>> Short, changing gmp memory allocator can cause segfaults in
>> various case where gnutls is used and initial
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Le 11/10/2014 02:24, Rasmus Lerdorf a écrit :
> On 10/10/2014 09:50 AM, Stas Malyshev wrote:
>> Hi!
>>
>>> Can you please elaborate a little ? Doesn't such leak have to
>>> be fixed in ext/gmp ?
>>
>> We clean up the memory at the end of the request.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Le 11/10/2014 07:37, Remi Collet a écrit :
> I will try to create a patch, for test, as we really need to fix
> this problem, especially it gmp going to go into core (bigint
> patch).
See
https://bugs.php.net/patch-display.php?bug=63595&
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Le 11/10/2014 08:17, Remi Collet a écrit :
> Le 11/10/2014 07:37, Remi Collet a écrit :
>
>> I will try to create a patch, for test, as we really need to fix
>> this problem, especially it gmp going to go into core (bigint
&
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
For a lot of time, PHP can use readline (default) or libedit (prefered
choice in all downstream) distribution.
Readline is GPLv3 so is not compatible with PHP License
I think is time to drop readline support (or, at least switch libedit
as the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
Bug 63520 is still not fixed.
We have 2 alternative extensions
- - jsonc the older one, probably not perfect, but used in a lot of
downstream distributions
- - jsond the recent one
I think it is time to switch ext/json to another implementat
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Le 10/10/2014 10:39, Remi Collet a écrit :
> Hi,
>
> See https://bugs.php.net/63595
>
>
> Short, changing gmp memory allocator can cause segfaults in
> various case where gnutls is used and initialized "before&quo
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Le 27/10/2014 09:03, Stas Malyshev a écrit :
> Hi!
>
> I'd like to have a vote on unserialize() improvement proposal
> outlined here: https://wiki.php.net/rfc/secure_unserialize
>
> soon-ish, but since discussion on it has been more than a year ago
>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Le 29/10/2014 00:35, Stas Malyshev a écrit :
> Hi!
>
>> phpdbg is under php.net ; every decision about phpdbg should then
>> be debatted with all the team, and new ideas, such as a protocol,
>> RFC'ed, whoever are the maintainers of the code. It's lik
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Le 30/10/2014 11:59, Bob Weinand a écrit :
> Also, just to point it out: Windows allows extensions to be in a
> random directory, *nix does not. I’d rather change the
> /acinclude.m4 to not be bound to the /ext directory, so that it
> just works like
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Le 07/11/2014 07:46, Dmitry Stogov a écrit :
> Commit:9dfa843a386b65b18353c510f032e322004d0bb7 Author:
> Dmitry Stogov Fri, 7 Nov 2014 09:46:49
> +0300 Parents: 0ddcf2a919a24cccb36bd0a69b05e6bbfc0bf883 Branches:
> PHP-5.4 PHP-5.5 PHP-5.6
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Le 14/11/2014 17:29, Remi Collet a écrit :
> Commit:23db11976889c3600cf7853fe0fd687a1c9435e6 Author: Remi
> Collet Fri, 14 Nov 2014 17:29:31 +0100
> Parents: faaea4f304cd6693e5f76c5a5d64d46e24326806 Branches:
> PHP
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
FPM state in 5.5.19 / 5.6.3 is quite bad :(
I just fix:
https://bugs.php.net/68420
listen=9000 listens to ipv6 localhost instead of all addresses
This is obviously a regression.
Ok, workaround exists, using explicit address which see
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Please see https://bugs.php.net/bug.php?id=68426
PHP >= 5.6 does not overwrite session file when session has not changed
Remi.
-BEGIN PGP SIGNATURE-
Version: GnuPG v2
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
iEYEARE
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Le 15/11/2014 08:27, Remi Collet a écrit :
I have also fixed:
https://bugs.php.net/68428
listen.allowed_clients is IPv4 only
> SO PLEASE, everyone who can test these patches, please test and
> give feedback [1]
Really
aM2
=zHh0
-END PGP SIGNATURE-
From 7b2c5a9463be7cdaeeb3c2962a769c3ea78bacec Mon Sep 17 00:00:00 2001
From: Remi Collet
Date: Mon, 17 Nov 2014 16:19:56 +0100
Subject: [PATCH] Add fcgi client library from
https://github.com/adoy/PHP-FastCGI-Client and more FPM tests
---
sapi/fpm/tests/005.phpt
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Le 19/11/2014 00:11, Levi Morrison a écrit :
> [1]: https://wiki.php.net/rfc/remove_php4_constructors
This will just kill PEAR and most of available libraries on PEAR forge.
Yes they are still some use of them
Yes keeping PHP 4 for PEAR is a bad idea
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I think the situation is now better.
At least test suite grow from 3 to 15 tests (+1 for Apparmor)
and all recent bugs / changes are covered.
Notice: test suite is 5.6+ only as rely on --force-stderr
Some minor changes are 5.6+ only
09f9f7ce503097
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Le 20/11/2014 10:34, Remi Collet a écrit :
> P.S. Still TODO: listen_allowed_clients is now aware of IPv4/IPv6,
> but it could make sense to make it aware of hostname (using
> getaddrinfo), and set all found addresses as allowed. Pro
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Le 28/11/2014 00:49, Ferenc Kovacs a écrit :
> Please test it carefully, and report any bugs in the bug system.
Please, especially FPM changes need our QA (see NEWS file).
All regression in 5.6.3 (related to IPv6) should be fixed.
So IPv4 should work
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Le 28/11/2014 08:50, Remi Collet a écrit :
> 5.6.4RC1 already built in Fedora rawhide, which means Koschei [1]
> will run (slowly, in the next days) a scratch rebuild of all the
> PHP stack, with the test suites (various libraries, phpunit,
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Le 28/11/2014 10:10, Dmitry Stogov a écrit :
> I see no problems with these patches. If all tests on PPC are
> passed, then they should be accepted. The patches won't affect
> other architectures.
>
> Anybody tested?
I should be able to run some scra
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
Please see and comment on https://bugs.php.net/68526
In this proposal, this is an optional feature:
- - new build option: --with-fpm-acl
=> no change for standard build
- - new config options: listen.users and listen.groups
=> no change for e
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Le 30/11/2014 10:35, Rowan Collins a écrit :
> Nit-picking, but I always find it awkward when two variable names
> differ only by an "s" - too easy to mistake one for the other,
> misread (or miswrite) documentation, etc. So perhaps
> listen.acl_users
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Le 30/11/2014 16:34, Levi Morrison a écrit :
>> This seems to be a small self contained feature. I'd like to be
>> able to implement this in 5.6+
>>
>> Is a RFC needed ?
>
> Is it possible for the ACL header to be in another location?
Patch refreshe
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Le 01/12/2014 04:37, Stanislav Malyshev a écrit :
> Hi Remi!
>
> I see that the test sapi/fpm/tests/015.phpt is randomly
> intermittently failing all the time in CI, making it harder to
> evaluate fixes. The cause of the failure is additional one or t
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Le 27/11/2014 13:39, Gustavo Frederico Temple Pedrosa a écrit :
> Hi, internals!
>
> There are some PRs for supports of PowerPC64
>
> https://github.com/php/php-src/pull/737
> https://github.com/php/php-src/pull/919
> https://github.com/php/php-src
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Le 01/12/2014 11:09, Remi Collet a écrit :
> Notice: master on ppc64 seems in quite bad shape, we currently
> have 111 failed tests (with ./configure --disable-all).
82 fixed
29 to work on...
Remi.
-BEGIN PGP SIGNATURE-
Version: Gn
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Mostly for Dmitry
After some work, I can reduce the failed tests number from 111 to 5 :)
(configure --disable-all)
Those seems related to new mm.
=> munmap() failed: [22] Invalid argument
Any idea on how to debug / fix them ?
Thanks,
Remi
P.S. I
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Le 02/12/2014 08:58, Remi Collet a écrit :
> Mostly for Dmitry
>
> After some work, I can reduce the failed tests number from 111 to 5
> :) (configure --disable-all)
>
> Those seems related to new mm. => munmap() failed: [2
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Le 02/12/2014 11:01, Lior Kaplan a écrit :
> Remi,
>
> Any chance to have these fixes for 5.5/5.6 as well?
All failed tests (and fix) are master only
related to move to size_t and new mm.
The only 5.6 issue (pack/unpack) have be fixed in 5.6+
Remi.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Le 02/12/2014 11:11, Andrea Faulds a écrit :
> Would you mind revealing which tests failed? This might be
> important to me with bigints.
See my previous mail in this thread failed tests are attached, but
most are fixed (well, I haven't test any exte
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
With latest commit (Thanks dmitry) test suite in ppc64 is now OK.
Remi.
-BEGIN PGP SIGNATURE-
Version: GnuPG v2
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
iEYEARECAAYFAlR9vY8ACgkQYUppBSnxahixCwCfbnQmf9/z6W17icpOErgJTOb
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Le 05/12/2014 17:17, Scott Arciszewski a écrit :
> Hi PHP Internals,
>
> I've been trying to get in contact with the maintainers of
> libmcrypt, but every response I've gotten was, "Oh, I haven't been
> a part of that for years."
>
> http://sourcefor
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Le 13/10/2014 22:15, Jakub Zelenka a écrit :
> Hi,
>
> We have 2 alternative extensions
>>
>> - - jsonc the older one, probably not perfect, but used in a lot
>> of downstream distributions
>>
>> - - jsond the recent one
>>
>>
>> I think it is tim
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Le 20/12/2014 23:01, F & N Laupretre a écrit :
> Hi,
>
>
>
> I don't know if this was discussed before. So, tell me what you
> think before I write an RFC.
>
>
>
> I would like to propose that namespaces, functions, and classes
> become case-sens
Le 27/12/2014 16:06, Sebastian Bergmann a écrit :
> Am 27.12.2014 um 16:01 schrieb Kalle Sommer Nielsen:
>> bugs going as far back as to PHP4.
>
> Bug reports for PHP version that are not supported anymore [1]
> should IMHO be bulk-closed. The message should ask to reopen if
> the bug is reproduc
1 - 100 of 344 matches
Mail list logo
