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, ByteStream\getStderr has a weird behaviour in my opnion when the standard error output is not available. which is that ByteStream\getStderr() returns a stream, but, it is not the expected STDERR stream, instead, its a php://memory stream that has been closed.
I would expect either:
return null indicating that the stream is not available
throw an exception informing me that the stream is not available
It would be good if this behaviour could be clarified maybe via documentation. and maybe introducing a new function that has a ( IMO ) saner behaviour?
currently,
ByteStream\getStderr
has a weird behaviour in my opnion when the standard error output is not available. which is thatByteStream\getStderr()
returns a stream, but, it is not the expectedSTDERR
stream, instead, its aphp://memory
stream that has been closed.I would expect either:
null
indicating that the stream is not availableIt would be good if this behaviour could be clarified maybe via documentation. and maybe introducing a new function that has a ( IMO ) saner behaviour?
For context, i was trying to replicate this:
which is possible to replicate with the current behaviour:
however, this implementation took me a bit of time to figure out as Amp does not mention anything about returning a closed stream from
getStderr
.The text was updated successfully, but these errors were encountered: