Doc #79166 [Ver]: Notices for read/write failures are not documented

From: Date: Mon, 27 Jan 2020 13:48:00 +0000
Subject: Doc #79166 [Ver]: Notices for read/write failures are not documented
References: 1  Groups: php.doc.bugs 
Request: Send a blank email to doc-bugs+get-17224@lists.php.net to get a copy of this message 
Edit report at https://bugs.php.net/bug.php?id=79166&edit=1

 ID:                 79166
 User updated by:    michael dot piche at csrt dot ulaval dot ca
 Reported by:        michael dot piche at csrt dot ulaval dot ca
 Summary:            Notices for read/write failures are not documented
 Status:             Verified
 Type:               Documentation Problem
 Package:            Streams related
 Operating System:   Windows
 PHP Version:        7.4
 Block user comment: N
 Private report:     N

 New Comment:

If it isn't possible to write to php://stderr, shouldn't the fopen return FALSE ? 

The notice come from Logger class in Symfony and there is a verification if the stream is a
ressource, with is the case.


Previous Comments:
------------------------------------------------------------------------
[2020-01-27 13:36:33] cmb@php.net

> No notice with the same code on 7.3.

That is to be expected, because that notice is only raised as of
PHP 7.4.0; formerly the write error has been silently ignored.
While this change is documented in the migration guide[1], it is
not yet documented in the manual proper, so I'm re-categorizing as
doc bug.

[1] <https://www.php.net/manual/en/migration74.incompatible.php#migration74.incompatible.core.fread-fwrite>

------------------------------------------------------------------------
[2020-01-27 13:28:52] michael dot piche at csrt dot ulaval dot ca

No notice with the same code on 7.3.

------------------------------------------------------------------------
[2020-01-27 08:03:23] cmb@php.net

I think so.  @michael, what do you mean with

> Everything is working fine with PHP 7.3.

No notice, or did you actually get some output?

------------------------------------------------------------------------
[2020-01-26 16:17:52] nikic@php.net

To clarify, the bug here is that you can open php://stderr despite the webserver SAPI presumably not
having an stderr FD?

------------------------------------------------------------------------
[2020-01-26 16:14:56] cmb@php.net

I can confirm that behavior for FastCGI/IIS.

------------------------------------------------------------------------


The remainder of the comments for this report are too long. To view
the rest of the comments, please view the bug report online at

    https://bugs.php.net/bug.php?id=79166


--
Edit this bug report at https://bugs.php.net/bug.php?id=79166&edit=1

Thread (8 messages)

« previous php.doc.bugs (#17224) next »