Official Go implementation of the Ethereum protocol

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.

Felföldi Zsolt 4eb9296910 p2p/nodestate: ensure correct callback order (#21436) ... This PR adds an extra guarantee to NodeStateMachine: it ensures that all immediate effects of a certain change are processed before any subsequent effects of any of the immediate effects on the same node. In the original version, if a cascaded change caused a subscription callback to be called multiple times for the same node then these calls might have happened in a wrong chronological order. For example: - a subscription to flag0 changes flag1 and flag2 - a subscription to flag1 changes flag3 - a subscription to flag1, flag2 and flag3 was called in the following order: [flag1] -> [flag1, flag3] [] -> [flag1] [flag1, flag3] -> [flag1, flag2, flag3] This happened because the tree of changes was traversed in a "depth-first order". Now it is traversed in a "breadth-first order"; each node has a FIFO queue for pending callbacks and each triggered subscription callback is added to the end of the list. The already existing guarantees are retained; no SetState or SetField returns until the callback queue of the node is empty again. Just like before, it is the responsibility of the state machine design to ensure that infinite state loops are not possible. Multiple changes affecting the same node can still happen simultaneously; in this case the changes can be interleaved in the FIFO of the node but the correct order is still guaranteed. A new unit test is also added to verify callback order in the above scenario.		4 years ago
..
discover	p2p/discover: fix typo in comments (#21554)	4 years ago
discv5	p2p/discv5: unset pingEcho on pong timeout (#21324)	5 years ago
dnsdisc	…
enode	…
enr	…
nat	p2p/nat: limit UPNP request concurrency (#21390)	5 years ago
netutil	…
nodestate	p2p/nodestate: ensure correct callback order (#21436)	4 years ago
simulations	node: refactor package node (#21105)	5 years ago
dial.go	…
dial_test.go	…
message.go	…
message_test.go	…
metrics.go	…
peer.go	p2p: measure packet throughput too, not just bandwidth	5 years ago
peer_error.go	…
peer_test.go	…
protocol.go	…
rlpx.go	p2p: measure packet throughput too, not just bandwidth	5 years ago
rlpx_test.go	…
server.go	…
server_test.go	…
util.go	…
util_test.go	…