summaryrefslogtreecommitdiff
path: root/vendor/google.golang.org/grpc/connectivity/connectivity.go
diff options
context:
space:
mode:
authorPaul Holzinger <pholzing@redhat.com>2021-08-18 20:59:37 +0200
committerPaul Holzinger <pholzing@redhat.com>2021-08-18 21:21:47 +0200
commit2d0a0c0d297f82891faee9e3a1a286d6f20fbdd2 (patch)
tree36ad5957b6246b144ed2d2d55b40efeb5c7fd11a /vendor/google.golang.org/grpc/connectivity/connectivity.go
parenta3d8b48fd56a722642f7cbcad52b2fa88f12b656 (diff)
downloadpodman-2d0a0c0d297f82891faee9e3a1a286d6f20fbdd2.tar.gz
podman-2d0a0c0d297f82891faee9e3a1a286d6f20fbdd2.tar.bz2
podman-2d0a0c0d297f82891faee9e3a1a286d6f20fbdd2.zip
fix rootlessport flake
When the rootlessport process is started the stdout/stderr are attached to the podman process. However once everything is setup podman exits and when the rootlessport process tries to write to stdout it will fail with SIGPIPE. The code handles this signal and puts /dev/null to stdout and stderr but this is not robust. I do not understand the exact cause but sometimes the process is still killed by SIGPIPE. Either go lost the signal or the process got already killed before the goroutine could handle it. Instead of handling SIGPIPE just set /dev/null to stdout and stderr before podman exits. With this there should be no race and no way to run into SIGPIPE errors. [NO TESTS NEEDED] Fixes #11248 Signed-off-by: Paul Holzinger <pholzing@redhat.com>
Diffstat (limited to 'vendor/google.golang.org/grpc/connectivity/connectivity.go')
0 files changed, 0 insertions, 0 deletions