Skip to content
New issue

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

devnet: blocktree bug causes finality to fail (and possibly other things) #2050

Closed
noot opened this issue Nov 18, 2021 · 1 comment · Fixed by #2060
Closed

devnet: blocktree bug causes finality to fail (and possibly other things) #2050

noot opened this issue Nov 18, 2021 · 1 comment · Fixed by #2060
Assignees

Comments

@noot
Copy link
Contributor

noot commented Nov 18, 2021

Task summary

  • on the devnet, I saw the following error:
2021-11-17T23:08:11Z WARN failed to play grandpa round: no common ancestor between two nodes: 0xf48c9edaf2da5ec19edb7ced855158d295ad00ed2108cec4c8e22a87e2b86d33 and 0xcf2b5f5b59def5e4df6ff2237cca1fda5e5d114c20e796a90a58ace1bd91c20d	grandpa.go:L346	pkg=grandpa

this error comes from the blocktree function HighestCommonAncestor which returns the common ancestor between two blocktree nodes with the highest number. however this error should NOT happen, as explained by the comment above the error:

	ancestor := an.highestCommonAncestor(bn)
	if ancestor == nil {
		// this case shouldn't happen - any two nodes in the blocktree must
		// have a common ancestor, the lowest of which is the root node
		return common.Hash{}, fmt.Errorf("%w: %s and %s", ErrNoCommonAncestor, a, b)
	}

when this function returns an error it causes grandpa to exit as it's an unexpected err, then finality stops.

fix the blocktree so this does not happen!!

@github-actions
Copy link

github-actions bot commented Dec 3, 2021

🎉 This issue has been resolved in version 0.6.0 🎉

The release is available on GitHub release

Your semantic-release bot 📦🚀

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants