aboutsummaryrefslogtreecommitdiffstats
path: root/graphql/graphql.go
diff options
context:
space:
mode:
authorFelix Lange <fjl@users.noreply.github.com>2019-04-08 19:35:11 +0800
committerPéter Szilágyi <peterke@gmail.com>2019-04-08 19:35:11 +0800
commited97517ff4db1982251d8bf7dbeca565159e3604 (patch)
treeb1bd8e769d00c22d77000ccd46b5ab642d3d04ed /graphql/graphql.go
parent3996bc1ad91665ad30036713fba11840a36dfff0 (diff)
downloadgo-tangerine-ed97517ff4db1982251d8bf7dbeca565159e3604.tar
go-tangerine-ed97517ff4db1982251d8bf7dbeca565159e3604.tar.gz
go-tangerine-ed97517ff4db1982251d8bf7dbeca565159e3604.tar.bz2
go-tangerine-ed97517ff4db1982251d8bf7dbeca565159e3604.tar.lz
go-tangerine-ed97517ff4db1982251d8bf7dbeca565159e3604.tar.xz
go-tangerine-ed97517ff4db1982251d8bf7dbeca565159e3604.tar.zst
go-tangerine-ed97517ff4db1982251d8bf7dbeca565159e3604.zip
p2p/discover: bump failure counter only if no nodes were provided (#19362)
This resolves a minor issue where neighbors responses containing less than 16 nodes would bump the failure counter, removing the node. One situation where this can happen is a private deployment where the total number of extant nodes is less than 16. Issue found by @jsying.
Diffstat (limited to 'graphql/graphql.go')
0 files changed, 0 insertions, 0 deletions