| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
As these hold on to some internal resource, there can't be two
"equal" objects with different identity. Make sure the lack of
public properties doesn't result in these being treated as always
equal.
|
| | |
| | |
| | |
| | | |
change" were moved, to be performed only if name/visibility had been really changed.
|
| | |
| | |
| | |
| | | |
Related to GH-6701
|
|\ \ \
| |/ /
| | |
| | |
| | | |
* PHP-8.0:
Fixed bug #80723
|
| | |
| | |
| | |
| | |
| | | |
This fixes the issue just for the Socket class. Presumably we'll
want to do the same for other "resource" objects.
|
| | |
| | |
| | |
| | |
| | | |
This is a hotfix for https://github.com/derickr/timelib/pull/94
until the issue is resolved upstream.
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Add CURLStringFile class which works similarly to CURLFile, but
uploads a file from a string rather than a file. This avoids the
need to create a temporary file, or use of a data:// stream.
Basic usage:
$file = new CURLStringFile($data, 'filename.txt', 'text/plain');
curl_setopt($curl, CURLOPT_POSTFIELDS, ['file' => $file]);
Closes GH-6456.
|
|\ \ \
| |/ /
| | |
| | |
| | | |
* PHP-8.0:
Suppress OpenSSL error on missing optional config
|
| |\ \
| | |/
| | |
| | |
| | | |
* PHP-7.4:
Suppress OpenSSL error on missing optional config
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
openssl_pkey_new() fetches various options from the config file --
most of these are optional, and not specifying them is not an error
condition from the perspective of the user. Unfortunately, the
CONF_get_string() API pushes an error when accessing a key that
doesn't exist (_CONF_get_string does not, but that is presumably a
private API). This commit adds a helper php_openssl_conf_get_string()
that automatically clears the error in this case. I've found that
OpenSSL occasionally does the same thing internally:
https://github.com/openssl/openssl/blob/22040fb790c854cefb04bed98ed38ea6357daf83/apps/req.c#L515-L517
Closes GH-6699.
|
|\ \ \
| |/ /
| | |
| | |
| | | |
* PHP-8.0:
Adapt test case for libcurl 7.75.0+
|
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
libcurl 7.75.0 finally adds support for `gophers://`, i.e. gopher over
TLS. The protocol is neither standardized, nor is the protocol
registered with IANA, but well, it is there and the test case should
cater to that.
|
|\ \ \
| |/ /
| | |
| | |
| | | |
* PHP-8.0:
Fixed bug #80747
|
| |\ \
| | |/
| | |
| | |
| | | |
* PHP-7.4:
Fixed bug #80747
|
| | |
| | |
| | |
| | | |
If RSA key generation fails, actually report that failure.
|
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
This is a read-only property for which Transliterator internally
assigns a string value.
Also clean up the code handling this property a bit.
|
| | |
| | |
| | |
| | |
| | | |
These are read-only properties, and Reflection makes sure to assign
only strings.
|
| | |
| | |
| | |
| | | |
Closes GH-6696
|
|\ \ \
| |/ /
| | |
| | |
| | | |
* PHP-8.0:
Fix #78680: mysqlnd pam plugin missing terminating null
|
| |\ \
| | |/
| | |
| | |
| | | |
* PHP-7.4:
Fix #78680: mysqlnd pam plugin missing terminating null
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
The PAM service requires the terminating null to be part
of the communication.
Tested with MariaDB-10.4(pam) and Percona Server 5.7.32(auth_pam_compat).
Also changed MySQL Enterprise test to the server side plugin, authentication_pam
as opposed to the client plugin mysql_clear_password.
Add additional check for pamtest user and pam service file as
all are required for the test.
More importantly, test result should actually succeed.
Thanks Geoff Montee for bug report.
Closes GH-78680.
|
|\ \ \
| |/ /
| | |
| | |
| | |
| | | |
* PHP-8.0:
Fix leak when breaking out of FilesystemIterator
Fixed bug #80600
|
| |\ \
| | |/
| | |
| | |
| | | |
* PHP-7.4:
Fix leak when breaking out of FilesystemIterator
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
We need to always destroy current, not just when iter.data is not
set.
Take this opportunity to clean up the iterator destructor code a
bit, to remove redundant checks and incorrect comments.
|
| | | |
|
| | |
| | |
| | |
| | |
| | |
| | | |
This feature has been completely removed.
Closes GH-6688.
|
| | | |
|
| | |
| | |
| | |
| | |
| | |
| | | |
reflection, session, shmop
Closes GH-6692
|
| | |
| | |
| | |
| | | |
Closes GH-6691
|
| | |
| | |
| | |
| | |
| | |
| | | |
This reverts commit 1106ff9a0e420e043c2e56c8ca00db85f1b85ee6.
Looks like this sauses segfaults on MacOs ZTS with JIT.
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
This deprecates passing null to non-nullable scale arguments of
internal functions, with the eventual goal of making the behavior
consistent with userland functions, where null is never accepted
for non-nullable arguments.
This change is expected to cause quite a lot of fallout. In most
cases, calling code should be adjusted to avoid passing null. In
some cases, PHP should be adjusted to make some function arguments
nullable. I have already fixed a number of functions before landing
this, but feel free to file a bug if you encounter a function that
doesn't accept null, but probably should. (The rule of thumb for
this to be applicable is that the function must have special behavior
for 0 or "", which is distinct from the natural behavior of the
parameter.)
RFC: https://wiki.php.net/rfc/deprecate_null_to_scalar_internal_arg
Closes GH-6475.
|
|\ \ \
| |/ /
| | |
| | |
| | | |
* PHP-8.0:
Fixed bug #80718
|
| | | |
|
|\ \ \
| |/ /
| | |
| | |
| | | |
* PHP-8.0:
Fixed bug #80719
|
| |\ \
| | |/
| | |
| | |
| | | |
* PHP-7.4:
Fixed bug #80719
|
| | | |
|
| | | |
|
| | |
| | |
| | |
| | |
| | |
| | | |
Tested with php-cgi and wordpress and 1255 for jit settings.
Closes GH-6659.
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
This changes ini_set() to accept all scalar types
(string|int|float|bool|null) for the new value. The idea here is
that while the INI system ultimately works with strings, its value
interpretation is designed to be consistent with PHP's casting rules,
e.g. "1" and "" are interpreted as boolean true and false respectively.
I personally believe that writing ini_set('precision', 10) makes more
sense than ini_set('precision', '10'), and find strict_types to be
unnecessarily pedantic here.
Closes GH-6680.
|
| | | |
|
| | |
| | |
| | |
| | | |
There are enough of them that sorting makes it a bit nicer.
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Some upcoming changes like https://wiki.php.net/rfc/deprecate_null_to_scalar_internal_arg
will make it somewhat inconvenient to determine whether a given
function invocation will generate a diagnostic. Rather than trying
to exclude this in advance, call the function with diagnostics
suppressed, and check whether anything was thrown.
This adds a new EG flag that is kept specific to the SCCP use-case.
This does not use the error_cb hook as it is a (non-TLS) global,
and doesn't fully suppress error handling besides.
Test this by removing the in advance checks for implode and array_flip.
|
|\ \ \
| |/ /
| | |
| | |
| | | |
* PHP-8.0:
Don't return null from password_get_info()
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
The get_info() handler should never fail, but even if it does,
we should still return a proper info array -- it doesn't make
sense that a completely incorrect hash returns an info array,
but a hash that is recognized but for which the options can't
be extracted would return null.
|
| | |
| | |
| | |
| | |
| | |
| | | |
zend_file_cache_unserialize_type().
Don't use scope of closures.
|
| | |
| | |
| | |
| | | |
argument/result type checks
|
| | | |
|
|\ \ \
| |/ /
| | |
| | |
| | | |
* PHP-8.0:
Make mysqli_ssl_set() arguments nullable
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
This function internally converts zero length arguments to NULL
argument -- but we should also accept them in the first place.
Null arguments being accepted was actually documented, before
bug #78399 adjusted the docs to match current behavior.
|
| | | |
|