mirror of https://github.com/containers/podman.git
c46884aa93
The function that's handing us events will return an error after closing the channel over which it's sending events, and its caller (in its own goroutine) will then send that error over another channel. The logic that started the goroutine is likely to notice that the events channel is closed before noticing that the error channel has a result for it to read, so any error that would have been communicated would be lost. When we finish reading events, check if the reader returned an error before telling our caller that there was no error. Signed-off-by: Nalin Dahyabhai <nalin@redhat.com> |
||
|---|---|---|
| .. | ||
| auth.go | ||
| changes.go | ||
| containers.go | ||
| containers_archive.go | ||
| containers_attach.go | ||
| containers_create.go | ||
| containers_export.go | ||
| containers_logs.go | ||
| containers_pause.go | ||
| containers_prune.go | ||
| containers_restart.go | ||
| containers_start.go | ||
| containers_stats_freebsd.go | ||
| containers_stats_linux.go | ||
| containers_stop.go | ||
| containers_top.go | ||
| containers_unpause.go | ||
| events.go | ||
| exec.go | ||
| images.go | ||
| images_build.go | ||
| images_history.go | ||
| images_prune.go | ||
| images_push.go | ||
| images_remove.go | ||
| images_save.go | ||
| images_search.go | ||
| images_tag.go | ||
| info.go | ||
| networks.go | ||
| ping.go | ||
| resize.go | ||
| secrets.go | ||
| system.go | ||
| types.go | ||
| unsupported.go | ||
| version.go | ||
| volumes.go | ||