History log of /php-src/sapi/fpm/tests/logreader.inc (Results 1 – 6 of 6)
Revision Date Author Comments
# 330cc5cd 13-Mar-2024 Máté Kocsis

Deprecate implicit nullable parameter types (#12959)

RFC: https://wiki.php.net/rfc/deprecate-implicitly-nullable-types

Co-authored-by: Gina Peter Banyard <girgias@php.net>


# 62682cbd 08-Dec-2023 Jakub Zelenka

Add FPM tester logs printing for all errors

Closes GH-12902


# 08b57772 12-Apr-2023 Joshua Behrens

Warn when fpm socket was not registered on the expected path

This might happen if the UDS length limit is exceeded.

Co-authored-by: Jakub Zelenka <bukka@php.net>

Closes GH-

Warn when fpm socket was not registered on the expected path

This might happen if the UDS length limit is exceeded.

Co-authored-by: Jakub Zelenka <bukka@php.net>

Closes GH-11066

show more ...


# 5a4520bc 21-Nov-2022 Jakub Zelenka

Fix bug #68207: Setting fastcgi.error_header can result in a WARNING


# 1c5844aa 29-Oct-2022 Jakub Zelenka

Fix GH-9754: SaltStack hangs when running php-fpm 8.1.11

SaltStack uses Python subprocess and redirects stderr to stdout which is
then piped to the returned output. If php-fpm starts in

Fix GH-9754: SaltStack hangs when running php-fpm 8.1.11

SaltStack uses Python subprocess and redirects stderr to stdout which is
then piped to the returned output. If php-fpm starts in daemonized mode,
it should close stderr. However a fix introduced in GH-8913 keeps stderr
around so it can be later restored. That causes the issue reported in
GH-9754. The solution is to keep stderr around only when php-fpm runs in
foreground as the issue is most likely visible only there. Basically
there is no need to restore stderr when php-fpm is daemonized.

show more ...


# 1e8fa660 04-Sep-2022 Jakub Zelenka

Rework FPM tests logging for better debugging