You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.

Daniel Nephin 29e93f6338 grpc: fix a data race by using a static resolver ... We have seen test flakes caused by 'concurrent map read and map write', and the race detector reports the problem as well (prevent us from running some tests with -race). The root of the problem is the grpc expects resolvers to be registered at init time before any requests are made, but we were using a separate resolver for each test. This commit introduces a resolver registry. The registry is registered as the single resolver for the consul scheme. Each test uses the Authority section of the target (instead of the scheme) to identify the resolver that should be used for the test. The scheme is used for lookup, which is why it can no longer be used as the unique key. This allows us to use a lock around the map of resolvers, preventing the data race.		4 years ago
..
internal/testservice	grpc: add Datacenter field to testing service response	4 years ago
resolver	grpc: fix a data race by using a static resolver	4 years ago
client.go	grpc: fix a data race by using a static resolver	4 years ago
client_test.go	grpc: fix a data race by using a static resolver	4 years ago
handler.go	Set gRPC keepalives to mirror Yamux keepalive behaviour	4 years ago
server_test.go	grpc: fix a data race by using a static resolver	4 years ago
stats.go	trim help strings to save a few bytes	4 years ago
stats_test.go	grpc: fix grpc metrics	4 years ago