ae538337ba
``` -bash-4.2$ tendermint show_validators panic: failed to determine gopath: exec: "go": executable file not found in $PATH goroutine 1 [running]: github.com/tendermint/tendermint/vendor/github.com/tendermint/tmlibs/common.gopath(0xc4200632c0, 0x18) /var/lib/jenkins/workspace/03.Build.Package/go/src/github.com/tendermint/tendermint/vendor/github.com/tendermint/tmlibs/common/os.go:26 +0x1b5 github.com/tendermint/tendermint/vendor/github.com/tendermint/tmlibs/common.init() /var/lib/jenkins/workspace/03.Build.Package/go/src/github.com/tendermint/tendermint/vendor/github.com/tendermint/tmlibs/common/os.go:17 +0x13c github.com/tendermint/tendermint/vendor/github.com/tendermint/go-wire.init() /var/lib/jenkins/workspace/03.Build.Package/go/src/github.com/tendermint/tendermint/vendor/github.com/tendermint/go-wire/wire.go:165 +0x50 github.com/tendermint/tendermint/vendor/github.com/tendermint/go-wire/data.init() /var/lib/jenkins/workspace/03.Build.Package/go/src/github.com/tendermint/tendermint/vendor/github.com/tendermint/go-wire/data/wrapper.go:89 +0x50 github.com/tendermint/tendermint/vendor/github.com/tendermint/tmlibs/cli.init() /var/lib/jenkins/workspace/03.Build.Package/go/src/github.com/tendermint/tendermint/vendor/github.com/tendermint/tmlibs/cli/setup.go:190 +0x76 main.init() /var/lib/jenkins/workspace/03.Build.Package/go/src/github.com/tendermint/tendermint/cmd/tendermint/main.go:42 +0x49``` An error message instead would be nice. ``` Now GoPath() is a function instead of a variable. |
||
---|---|---|
.. | ||
test_data | ||
types | ||
README.md | ||
byzantine_test.go | ||
common.go | ||
common_test.go | ||
mempool_test.go | ||
reactor.go | ||
reactor_test.go | ||
replay.go | ||
replay_file.go | ||
replay_test.go | ||
state.go | ||
state_test.go | ||
ticker.go | ||
version.go | ||
wal.go |
README.md
The core consensus algorithm.
- state.go - The state machine as detailed in the whitepaper
- reactor.go - A reactor that connects the state machine to the gossip network
Go-routine summary
The reactor runs 2 go-routines for each added peer: gossipDataRoutine and gossipVotesRoutine.
The consensus state runs two persistent go-routines: timeoutRoutine and receiveRoutine. Go-routines are also started to trigger timeouts and to avoid blocking when the internalMsgQueue is really backed up.
Replay/WAL
A write-ahead log is used to record all messages processed by the receiveRoutine, which amounts to all inputs to the consensus state machine: messages from peers, messages from ourselves, and timeouts. They can be played back deterministically at startup or using the replay console.