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
Occasionally when running the node I've seen this panic, causing the node to crash:
panic: send on closed channel goroutine 56677 [running]: github.com/ChainSafe/gossamer/dot/state.(*BlockState).notifyImported.func1(0xc005da4120, 0xc005f02780) /home/ubuntu/gossamer/dot/state/block_notify.go:107 +0x3f created by github.com/ChainSafe/gossamer/dot/state.(*BlockState).notifyImported /home/ubuntu/gossamer/dot/state/block_notify.go:105 +0x1ae
need to make sure there are no writes to channels that are potentially closed
Steps to reproduce the behaviour:
This happens quite infrequently, so not sure how to reproduce it other than running the node a bunch of times
The text was updated successfully, but these errors were encountered:
grandpa_subscribeJustifications
🎉 This issue has been resolved in version 0.6.0 🎉
The release is available on GitHub release
Your semantic-release bot 📦🚀
Sorry, something went wrong.
edwardmack
Successfully merging a pull request may close this issue.
Describe the bug
Occasionally when running the node I've seen this panic, causing the node to crash:
need to make sure there are no writes to channels that are potentially closed
To Reproduce
Steps to reproduce the behaviour:
This happens quite infrequently, so not sure how to reproduce it other than running the node a bunch of times
The text was updated successfully, but these errors were encountered: