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
I'm not sure if this is intended or not, but enabling captureCombined will make getBuffers return CapturingBufferWriter for both stdout and stderr instead of PipedBuffer. The problem is that when calling the constructor of CommandChild, it checks against instances of PipedBuffer only, making it pass undefined to both buffers and making any call to CommandChild.{stdout,stderr}() fail in the assertion function.
I was expecting to be able to access the streams even when I wanted a combined buffer too.
The text was updated successfully, but these errors were encountered:
Sorry, can you say on a higher level what the issue is when using the API (not about what's going on internally because it's changing a lot) and maybe provide an example of some code erroring?
I'm not sure if this is intended or not, but enabling
captureCombined
will makegetBuffers
returnCapturingBufferWriter
for both stdout and stderr instead ofPipedBuffer
. The problem is that when calling the constructor ofCommandChild
, it checks against instances ofPipedBuffer
only, making it passundefined
to both buffers and making any call toCommandChild.{stdout,stderr}()
fail in the assertion function.I was expecting to be able to access the streams even when I wanted a combined buffer too.
The text was updated successfully, but these errors were encountered: