client: call .Endpoints() in dial() in client/v3/client.go instead of accessing cfg.Endpoints directly

[yishuT]

etcd/client/v3/client.go

Line 299 in 0cdd558

initialEndpoints := strings.Join(c.cfg.Endpoints, ";")

accesses
endpoints without acquiring lock. Fix it to call Endpoints()

Fix #13201

[serathius]

I agree that this variable needs a lock to prevent data race with SetEndpoints, but I would also not expect that SetEndpoints should modify Config.
I would not expect config structs like client.v3.Config to be ever mutated by consumers. I expect that SetEndpoints was added later. Mutex withing Client doesn't directly specify which variables are protected by it.

Instead of of just adding lock, maybe we should consider adding dedicated endpoint field to Client struct and specifying explicitly that is protected by mutex?

[yishuT]

yeah, I agree. I only fixed what our race detector complained but didn't read the code in detail. There is one thing that if SetEndpoints is called for a new list of endpoints after client is init, now this client has two different list of endpoints, one in client.cfg, the other in client.endpoint.

[yishuT]

nvm, we don't do deep copy in SetEndpoints

[serathius]

LG

[yishuT]

any updates, or should I do something?

[spzala]

lgtm. Can you please squash commits into one? Thanks @yishuT

[yishuT]

squash commits

[spzala]

squash commits

Thanks!
CI is good, also tested locally.