4fab22d691
we spawned a goroutine to wait on the context's done channel sending the error afterward, but we forgot to ensure the context was eventually done, so the goroutine would be leaked until then. instead, we can just do a select on two channels to get the error rather than spawn a goroutine which makes it impossible to leak a goroutine. Change-Id: I2fdba206ae6ff7a3441b00708b86b36dfeece2b5 |
||
|---|---|---|
| .. | ||
| rpcpeer | ||
| rpcstatus | ||
| common_drpc.go | ||
| common_grpc.go | ||
| common.go | ||
| compat_drpc.go | ||
| compat_grpc.go | ||
| conn.go | ||
| dial_drpc.go | ||
| dial_grpc.go | ||
| dial.go | ||
| gen.go | ||
| rpc_test.go | ||