Skip to content

Conversation

Frozen
Copy link
Contributor

@Frozen Frozen commented Dec 21, 2024

I faced with log message like this one
"shardID":0,"myBlock":3,"myViewID":2,

the only one way how it's possible is https://github.com/harmony-one/harmony/blob/dev/consensus/consensus_v2.go#L399 where we set block number, but not view id. I checked logs, and it shows that method syncNotReadyChan was called.

@Frozen Frozen self-assigned this Dec 21, 2024
@Frozen Frozen marked this pull request as draft December 21, 2024 04:07
@Frozen Frozen marked this pull request as ready for review December 23, 2024 18:16
@sophoah
Copy link
Contributor

sophoah commented Jan 29, 2025

The PR looks fine. It's important to note that this change only applies when the node is syncing. Consensus operations should not be active during synchronization.

@sophoah
Copy link
Contributor

sophoah commented Jan 29, 2025

cc @GheisMohammadi thanks for review and approval

@GheisMohammadi
Copy link
Contributor

syncNotReadyChan notifies the consensus that it is not fully synchronized, transitioning it to Syncing mode. But why do we need to increment the consensus block and viewID?

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 this pull request may close these issues.

3 participants