| #
858d0c09 |
| 06-Aug-2021 |
Jeremy Mikola |
Include class name in Serializable deprecation message
The deprecation message was originally introduced in 3e6b447 (#6494).
I first encountered this notice when testing the MongoDB
Include class name in Serializable deprecation message
The deprecation message was originally introduced in 3e6b447 (#6494).
I first encountered this notice when testing the MongoDB extension
with PHP 8.1, which produced many duplicate messages that provided
no detail about the particular class that needed to be fixed.
Closes GH-7346.
show more ...
|
| #
1a370d33 |
| 30-Jul-2021 |
Nikita Popov |
Skip some tests under --preload
A genuine problem here is that we sometime get different class
casing due interaction with the ZSTR CE cache. Ignore these for
now. |
| #
3e6b4479 |
| 07-Dec-2020 |
Nikita Popov |
Partially deprecate Serializable
If Serializable is implemented, require that __serialize() and
__unserialize() are implemented as well, else issue a deprecation
warning.
Al
Partially deprecate Serializable
If Serializable is implemented, require that __serialize() and
__unserialize() are implemented as well, else issue a deprecation
warning.
Also deprecate use of PDO::FETCH_SERIALIZE.
RFC: https://wiki.php.net/rfc/phase_out_serializable
Closes GH-6494.
show more ...
|
| #
c37a1cd6 |
| 10-Sep-2020 |
Máté Kocsis |
Promote a few remaining errors in ext/standard
Closes GH-6110 |
| #
d30cd7d7 |
| 26-May-2020 |
Máté Kocsis |
Review the usage of apostrophes in error messages
Closes GH-5590 |
| #
1f48feeb |
| 13-Apr-2020 |
Máté Kocsis |
Improve some TypeError and ValueError messages
Closes GH-5377 |
| #
0b4778c3 |
| 16-Jan-2020 |
Máté Kocsis |
Fix #78880: Another bunch of spelling errors |
| #
3b0a1905 |
| 10-Dec-2019 |
Máté Kocsis |
Promote warning to exception in unserialize() |
|
Revision tags: php-7.3.13RC1, php-7.2.26RC1, php-7.4.0, php-7.2.25, php-7.3.12, php-7.4.0RC6, php-7.3.12RC1, php-7.2.25RC1, php-7.4.0RC5, php-7.1.33, php-7.2.24, php-7.3.11, php-7.4.0RC4, php-7.3.11RC1, php-7.2.24RC1 |
|
| #
81d95c4c |
| 07-Oct-2019 |
Nikita Popov |
Don't test default serialize max_depth
The default depth is large enough to cause stack overflows in
msan builds, though apparently only on old clang versions. Avoiding
a stack overf
Don't test default serialize max_depth
The default depth is large enough to cause stack overflows in
msan builds, though apparently only on old clang versions. Avoiding
a stack overflow there requires making the depth *much* smaller,
less than 1000. As I don't think that's reasonable for all the other
setups where 4k works fine, I'm just dropping this part of the test.
show more ...
|
|
Revision tags: php-7.4.0RC3, php-7.2.23 |
|
| #
1806ce9c |
| 24-Sep-2019 |
Nikita Popov |
Add max_depth option to unserialize()
Add a max_depth option to unserialize and an unserialize_max_depth
ini setting, which can be used to control the depth limit. The
default value
Add max_depth option to unserialize()
Add a max_depth option to unserialize and an unserialize_max_depth
ini setting, which can be used to control the depth limit. The
default value is 4096.
This option is intended to prevent stack overflows during the
unserialization of deeply nested structures.
This fixes bug #78549 and addresses oss-fuzz #17581, #17589, #17664,
and #17788.
show more ...
|
