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

[Bug]: Consensus error, but node continues to run normally and produce blocks. #22625

Closed
1 task done
fiamma-builder opened this issue Nov 23, 2024 · 6 comments
Closed
1 task done
Assignees
Labels

Comments

@fiamma-builder
Copy link

fiamma-builder commented Nov 23, 2024

Is there an existing issue for this?

  • I have searched the existing issues

What happened?

Image

Cosmos SDK Version

v0.50.9

How to reproduce?

I used the Ignite to build a chain, and the Cosmos SDK version is v0.50.9.
Image

I deployed four nodes on Amazon Web Services, and these nodes used private IP addresses as their seed nodes. After the network started, there were no error messages at first, but after running for some time, such log information appeared, but the network continued to run normally and produce blocks as usual.

@tac0turtle
Copy link
Member

thank you for the issue. Did you add in any custom modules?

@fiamma-builder
Copy link
Author

thank you for the issue. Did you add in any custom modules?

https://github.com/fiamma-chain/fiamma/blob/main/app/babylon.go My project does indeed depend on an external Babylon module, but I did not modify the consensus module code, just normally wrote my business logic

@tac0turtle
Copy link
Member

does the babylon code introduce any vote extensions? this issue is with consensus less so cosmos sdk but we can help

@fiamma-builder
Copy link
Author

The Babylon module code we introduced has not included any voting extensions; here is the link to its repository. https://github.com/babylonlabs-io/babylon-sdk

@tac0turtle tac0turtle self-assigned this Nov 27, 2024
@tac0turtle
Copy link
Member

sorry for the delay in responding, are you still running into this issue?

@tac0turtle
Copy link
Member

closing this issue as it seems the issue is not cosmos sdk but possibly from the comet side. im not sure why it would be presnt

@tac0turtle tac0turtle closed this as not planned Won't fix, can't repro, duplicate, stale Dec 19, 2024
@github-project-automation github-project-automation bot moved this from 📋 Backlog to 🥳 Done in Cosmos-SDK Dec 19, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
Status: 🥳 Done
Development

No branches or pull requests

2 participants