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
The STDERR constant is only available in the php CLI. The send method will generally be called from the web server (for logging, publishing, etc).
You end up with notices and warnings like:
<b>Notice</b>: Use of undefined constant STDERR - assumed 'STDERR' in <b><PATH>/google-cloud-php/src/Core/Batch/BatchTrait.php</b> on line <b>107</b><br />
<br />
<b>Warning</b>: fwrite() expects parameter 1 to be resource, string given in <b><PATH>/google-cloud-php/src/Core/Batch/BatchTrait.php</b> on line <b>111</b><br />
<br />
<b>Notice</b>: Use of undefined constant STDERR - assumed 'STDERR' in <b><PATH>/google-cloud-php/src/Core/Batch/BatchTrait.php</b> on line <b>116</b><br />
<br />
<b>Warning</b>: fwrite() expects parameter 1 to be resource, string given in <b><PATH>/google-cloud-php/src/Core/Batch/BatchTrait.php</b> on line <b>118</b><br />
The text was updated successfully, but these errors were encountered:
I do agree that either way, however, this isn't ideal. I believe it would be best to provide a more thorough avenue to manage debug output. One thing we have considered is providing the ability to input a PSR-3 based logger. For a little more context, we have #586. We hope to flesh this out more soon!
See:
The
STDERR
constant is only available in the php CLI. Thesend
method will generally be called from the web server (for logging, publishing, etc).You end up with notices and warnings like:
The text was updated successfully, but these errors were encountered: