We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Describe the bug shard 1 devnet with leader rotation activated faced a segmentation fault after deletion of the shard 0 DB and restart
[signal SIGSEGV: segmentation violation code=0x1 addr=0x30 pc=0x1aa075f] goroutine 2436 [running]: github.com/harmony-one/harmony/consensus.(*Consensus).isLeader(0x22?) /root/go/src/github.com/harmony-one/harmony/consensus/consensus_service.go:491 +0x1f github.com/harmony-one/harmony/consensus.(*Consensus).StartChannel(0xc00d3f8f00) /root/go/src/github.com/harmony-one/harmony/consensus/consensus_v2.go:332 +0x36 github.com/harmony-one/harmony/node.(*Node).BootstrapConsensus.func2() /root/go/src/github.com/harmony-one/harmony/node/node_handler.go:437 +0x25 created by github.com/harmony-one/harmony/node.(*Node).BootstrapConsensus /root/go/src/github.com/harmony-one/harmony/node/node_handler.go:436 +0x1af
To Reproduce Steps to reproduce the behavior:
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Describe the bug
shard 1 devnet with leader rotation activated faced a segmentation fault after deletion of the shard 0 DB and restart
To Reproduce
Steps to reproduce the behavior:
The text was updated successfully, but these errors were encountered: