#
1a66d647 |
| 16-Dec-2020 |
Nikita Popov |
Merge branch 'PHP-7.4' into PHP-8.0 * PHP-7.4: Fixed bug #67983
|
#
315f3f8d |
| 16-Dec-2020 |
Nikita Popov |
Fixed bug #67983 We need to check the BIT case first, otherwise it will get skipped in INT_AND_FLOAT_NATIVE mode. |
#
f6bd3dfd |
| 16-Dec-2020 |
Nikita Popov |
Merge branch 'PHP-7.4' into PHP-8.0 * PHP-7.4: Fix bug #80523
|
#
118ff033 |
| 16-Dec-2020 |
Nikita Popov |
Fix bug #80523 Don't truncate the file length to unsigned int... I have no idea whether that fully fixes the problem because the process gets OOM killed before finishing, but at
Fix bug #80523 Don't truncate the file length to unsigned int... I have no idea whether that fully fixes the problem because the process gets OOM killed before finishing, but at least the immediate parse error is gone now.
show more ...
|
#
078cdd8f |
| 15-Dec-2020 |
Derick Rethans |
Prepare for 7.4.15 |
#
f1f78ac8 |
| 15-Dec-2020 |
Gabriel Caruso |
Next is 8.0.2 |
#
c2fbab39 |
| 15-Dec-2020 |
Christoph M. Becker |
Merge branch 'PHP-7.4' into PHP-8.0 * PHP-7.4: Fix #77322: PharData::addEmptyDir('/') Possible integer overflow
|
#
a53d67ce |
| 11-Dec-2020 |
Christoph M. Becker |
Fix #77322: PharData::addEmptyDir('/') Possible integer overflow `phar_path_check()` already strips a leading slash, so we must not attempt to strip the trailing slash from an now empty
Fix #77322: PharData::addEmptyDir('/') Possible integer overflow `phar_path_check()` already strips a leading slash, so we must not attempt to strip the trailing slash from an now empty directory name. Closes GH-6508.
show more ...
|
#
40d9e3ab |
| 15-Dec-2020 |
Christoph M. Becker |
7.3.27 is next |
#
66e39070 |
| 14-Dec-2020 |
Dmitry Stogov |
Fixed bug #80506 (Immediate SIGSEGV upon ini_set("opcache.jit_debug", 1)) |
#
d2540780 |
| 13-Dec-2020 |
Jakub Zelenka |
Merge branch 'PHP-7.4' into PHP-8.0
|
#
a221e17b |
| 28-Nov-2020 |
Jakub Zelenka |
Fix bug #69625: FPM returns 200 status on request without SCRIPT_FILENAME |
#
ccb7f1c7 |
| 11-Dec-2020 |
Nikita Popov |
Fixed bug #79132 Following cmb's suggestion and replacing the counter with a check against the bound_params HT, which ensures that both cannot go out of sync. |
#
ad8eb116 |
| 11-Dec-2020 |
Nikita Popov |
Fixed bug #67004 Repeated execute() with native PS failed to release the previous result set on libmysqlclient. Move freeing the result set into a common location. |
#
43741a3f |
| 11-Dec-2020 |
Nikita Popov |
Fixed bug #62889 Our minimum libmysqlclient version requirement is high enough that we don't need to check for MYSQL_OPT_LOCAL_INFILE support. However, the mysql_get_option() fu
Fixed bug #62889 Our minimum libmysqlclient version requirement is high enough that we don't need to check for MYSQL_OPT_LOCAL_INFILE support. However, the mysql_get_option() function seems to only be available since 5.7 (though it's really hard to find any definitie information on when MySQL introduced certain functions or changes...) so we need to store the value of the flag locally to make it available through getAttribute().
show more ...
|
#
9e3ba775 |
| 10-Dec-2020 |
Nikita Popov |
Fixed bug #72368 Generate a param count mismatch error even if the query contains no placeholders. Additionally we shouldn't HANDLE errors from pdo_parse_params, which are a
Fixed bug #72368 Generate a param count mismatch error even if the query contains no placeholders. Additionally we shouldn't HANDLE errors from pdo_parse_params, which are always reported via raise_impl_error. Doing so results in duplicate error messages.
show more ...
|
#
15b51a21 |
| 10-Dec-2020 |
Nikita Popov |
Fixed bug #79131 When a driver reports an error during EVT_ALLOC (and some over EVTs), make sure we handle it as usual, i.e. warn or throw. This requires some adjustments in PDO
Fixed bug #79131 When a driver reports an error during EVT_ALLOC (and some over EVTs), make sure we handle it as usual, i.e. warn or throw. This requires some adjustments in PDO PgSQL to stop manually doing this through an impl error. Unfortunately the PDO PgSQL error messages regress because of this, as they now include a completely arbitrary error code. There doesn't seem to be an ability to skip it right now.
show more ...
|
#
288581fa |
| 10-Dec-2020 |
Nikita Popov |
Fixed bug #79872 by improving error message The actual behavior here is correct, but the previous error message was misleading, as neither fetchAll() nor buffered queries would help
Fixed bug #79872 by improving error message The actual behavior here is correct, but the previous error message was misleading, as neither fetchAll() nor buffered queries would help in this situation. Instead it is necessary to consume all rowsets, which can be done by either unsetting the statement or calling closeCursor().
show more ...
|
#
d63aedd1 |
| 10-Dec-2020 |
Nikita Popov |
Merge branch 'PHP-7.4' into PHP-8.0 * PHP-7.4: Fixed bug #76815
|
#
e450621f |
| 10-Dec-2020 |
Nikita Popov |
Fixed bug #76815 When we receive an error while reading a result set, we should assume that no more result sets are available. libmysqlclient implements the same behavior. |
#
9b678bc4 |
| 10-Dec-2020 |
Nikita Popov |
Merge branch 'PHP-7.4' into PHP-8.0 * PHP-7.4: Fixed bug #71145
|
#
49220492 |
| 10-Dec-2020 |
Nikita Popov |
Fixed bug #71145 Consume any additional result sets when running INIT_COMMAND. |
#
f3d58778 |
| 09-Dec-2020 |
Nikita Popov |
Backport fix for bug #70066 Given the number of duplicates this bug report had, it seems worthwhile to fix this on PHP-7.4 as well. Cherry-pick of 106e7e4bca7c0fd975eb219b18e3c3
Backport fix for bug #70066 Given the number of duplicates this bug report had, it seems worthwhile to fix this on PHP-7.4 as well. Cherry-pick of 106e7e4bca7c0fd975eb219b18e3c34957ba8657.
show more ...
|
#
106e7e4b |
| 09-Dec-2020 |
Nikita Popov |
Fixed bug #70066 If we fall back to emulated prepared statements, destroy S->stmt, so the code doesn't get confused about which mode we're in. |
#
fcfa7fd0 |
| 09-Dec-2020 |
Nikita Popov |
Fixed bug #66878 Keep track of whether we have fully consumed all result sets, either using nextRowset() calls or closeCursor() and skip the attempt to consume remaining results sets
Fixed bug #66878 Keep track of whether we have fully consumed all result sets, either using nextRowset() calls or closeCursor() and skip the attempt to consume remaining results sets during destruction in that case. Especiall if closeCursor() has been used, we really shouldn't have this sort of cross-statement inference.
show more ...
|