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
This might've been the cause for the flaky test we saw, because the docs
say that `cmd.Run()` in combination with `StdoutPipe`/`StderrPipe` is
wrong:
> `Wait` will close the pipe after seeing the command exit, so most callers
> need not close the pipe themselves. It is thus incorrect to call `Wait`
> before all reads from the pipe have completed. For the same reason, it
> is incorrect to call `Run` when using `StdoutPipe`. See the example for
> idiomatic usage.
See: https://pkg.go.dev/os/exec#example-Cmd.StdoutPipe
0 commit comments