On 29.12.2018 at 01:02, Stanislav Malyshev wrote:
>
>> As for me, the question is not *if*, but rather *when* and *how* this
>> inconsistency should be resolved. Regarding the *when*, it seems to me
>
> If you mean that loading "0.3" from string would suddenly stop working
> in Germany, then neve
On 30/12/2018 23:29, Stanislav Malyshev wrote:
Hi!
There are 2 ways out:
* This PR https://github.com/php/php-src/pull/3698 aims to solve the
root cause: it modifies tests in order to make them generate
certificates on the fly and always be sure that their expiration date is
in the future (and
Hi!
> There are 2 ways out:
> * This PR https://github.com/php/php-src/pull/3698 aims to solve the
> root cause: it modifies tests in order to make them generate
> certificates on the fly and always be sure that their expiration date is
> in the future (and also unties lots of tests from single ce
On 02/12/2018 09:16, Stanislav Malyshev wrote:
Hi!
I am seeing tons of broken openssl tests on Travis CI. Example:
https://travis-ci.org/php/php-src/jobs/462367522
All errors seem to be the same:
001+ Warning: stream_socket_client(): SSL operation failed with code 1.
OpenSSL Error messages:
002
"Christoph M. Becker" in php.internals (Sat, 29 Dec 2018 12:27:58 +0100):
>As I understand it, the extension would not be compiled by default, but
>rather has to be enabled using an explicit --with-ffi configure
>option[1] (or --enable-ffi on Windows[2]).
A strange difference. Is not the conventio
