-
Notifications
You must be signed in to change notification settings - Fork 677
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
Fix: Conditional logging for 'Proceeding to mine blocks' message #5338
Fix: Conditional logging for 'Proceeding to mine blocks' message #5338
Conversation
…ch 3 and shutdown the runloop Signed-off-by: Jacinta Ferrant <jacinta@trustmachines.co>
… into chore/fix-multiple-miners
…d update the README file Signed-off-by: Jacinta Ferrant <jacinta@trustmachines.co>
Signed-off-by: Jacinta Ferrant <jacinta@trustmachines.co>
Signed-off-by: Jacinta Ferrant <jacinta@trustmachines.co>
…tate between (and including) the new and old tips, since cached data from the old tip will have stored a negative cache result that ought now to be positive in the context of the new tip.
…og analysis tools
…e-key-leakage Do not leak a private key that has a small typo
… into chore/remove-v1-signer
…tent with no-caching behavior
… into chore/fix-multiple-miners
Chore/remove v1 signer
Chore: Merge master -> develop
Signed-off-by: Jacinta Ferrant <jacinta@trustmachines.co>
… into chore/fix-multiple-miners
Signed-off-by: Jacinta Ferrant <jacinta@trustmachines.co>
…ure_height Include `tenure_height` in `/new_block` event payload
Signed-off-by: Jacinta Ferrant <jacinta@trustmachines.co>
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Good idea. Thanks for the PR @Parikalp-Bhardwaj!
Fix partial tenure fork test
Should we target this to |
Yes, good point. |
@Parikalp-Bhardwaj : This should merge to develop instead of master before we can approve |
…ions Add version to signer messages
Chore: Configure signer set to be more permissive about a slow miner wakeup
Chore: Set 3.0 mainnet activation height
Replaced with #5348 |
Fix: Conditional logging for 'Proceeding to mine blocks' message #5338
This pull request has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
Summary
This PR fixes an issue where the node logs
Proceeding to mine blocks
even when running as a follower node. The log message is now conditional on the node being a miner.Changes
Related Issues