Files
tendermint/p2p
Alexander Simmerl 50ae892d5e p2p: Keep reference to connections in test peer
We observed non-deterministic test failures in one of our switch tests,
which would happen if the GC would run between iterations of the accept
loop. As we don't hold any reference to the connection the setup
finalizer might get triggered and therefore the file handle closed. For
the curious check the references on finalizers and the variable scoping
in the spec:

https://groups.google.com/forum/#!topic/golang-nuts/xWkhGJ5PY6c
https://groups.google.com/forum/#!topic/golang-nuts/d8aF4rAob7U/discussion
https://golang.org/ref/spec#Declarations_and_scope

Fixes #1266
2018-03-19 20:35:12 +01:00
..
2018-02-27 18:01:10 +04:00
2018-02-12 14:32:09 +04:00
2017-11-27 22:39:11 +00:00
2017-04-21 18:07:52 -04:00
2018-01-21 00:34:41 -05:00
2017-11-27 22:39:12 +00:00
2018-01-21 00:34:41 -05:00
2018-01-21 00:34:41 -05:00
2018-01-21 00:34:41 -05:00
2018-01-21 00:34:41 -05:00
2018-01-21 00:34:41 -05:00
2018-03-19 13:19:05 +03:00
2018-03-06 17:36:44 +01:00
2018-01-21 00:34:41 -05:00
2017-04-21 18:07:52 -04:00

p2p

The p2p package provides an abstraction around peer-to-peer communication.

Docs:

  • Connection for details on how connections and multiplexing work
  • Peer for details on peer ID, handshakes, and peer exchange
  • Node for details about different types of nodes and how they should work
  • Pex for details on peer discovery and exchange
  • Config for details on some config option