You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently the output (Could not open input file: non-existent.php) is sent to stdout but it should be sent to stderr instead.
I have discovered when using php for interprocess communication where the stdout might be consumed as regular data causing protocol failure hard to understand, as in my case, only the first 4 bytes were consumed (and from Coul it was hard to identify the problem). Simply said, stdout should never contain any other data then data printed by a valid script.
The text was updated successfully, but these errors were encountered:
Looks like php_printf is used a bit in main/ and SAPIs for this - and if we're counting sundry diagnostic information, even more in extensions and Zend/. It probably shouldn't.
I grepped for php_printf cases in main/ and sapi/ and converted the
cases which clearly indicate errors to fprintf(stderr, ...), like
suggested in the linked issue.
I grepped for php_printf cases in main/ and sapi/ and converted the
cases which clearly indicate errors to fprintf(stderr, ...), like
suggested in the linked issue.
Description
Repro command:
php non-existent.php
Currently the output (
Could not open input file: non-existent.php
) is sent to stdout but it should be sent to stderr instead.I have discovered when using php for interprocess communication where the stdout might be consumed as regular data causing protocol failure hard to understand, as in my case, only the first 4 bytes were consumed (and from
Coul
it was hard to identify the problem). Simply said, stdout should never contain any other data then data printed by a valid script.The text was updated successfully, but these errors were encountered: