#Include stderr in provisioning error
1 messages · Page 1 of 1 (latest)
Since the engine logs are going to stderr, let's say there's a failure midway through a pipeline run (e.g., docker shuts down), then the error that's going to be printed to the user is going to not only be huge, but also duplicated, right?
In the go implementation the output is only buffered while that StartEngineSession is running, there's a defer that stops the buffering at the end of it. So the buffer should only be filled and returned if there is an error while connecting to the session, not later while pipelines are actually being executed
Makes sense, thanks 👍
Is this being done in node?