Erik Grinaker
4dca066aab
This test occasionally fails because the peer is already stopped. It is unclear to me exactly what this test is supposed to do, since calling `FlushStop()` will stop the peer, but the test asserts that the peer shouldn't have been stopped by `FlushStop()` since calling `Stop()` afterwards will error in that case. The current PEX reactor will be removed in the new P2P stack anyway. |
4 years ago | |
---|---|---|
.. | ||
addrbook.go | p2p: rename ID to NodeID | 4 years ago |
addrbook_test.go | p2p: rename ID to NodeID | 4 years ago |
errors.go | p2p: ensure peers can't change IP of known nodes (#5136) | 4 years ago |
file.go | linter: (1/2) enable errcheck (#5064) | 4 years ago |
known_address.go | p2p: rename ID to NodeID | 4 years ago |
params.go | fix build and test | 7 years ago |
pex_reactor.go | proto/p2p: rename PEX messages and fields (#5974) | 4 years ago |
pex_reactor_test.go | test: disable TestPEXReactorSeedModeFlushStop due to flake (#5996) | 4 years ago |
reactor.go | p2p: resolve PEX addresses in PEX reactor (#5980) | 4 years ago |