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

Fix: Conditional logging for 'Proceeding to mine blocks' message #5338

Closed

Conversation

Parikalp-Bhardwaj
Copy link
Contributor

@Parikalp-Bhardwaj Parikalp-Bhardwaj commented Oct 21, 2024

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

  • Added a conditional check around the log message to ensure it only appears when the node is configured as a miner.

Related Issues

jferrant and others added 30 commits September 26, 2024 14:39
…ch 3 and shutdown the runloop

Signed-off-by: Jacinta Ferrant <jacinta@trustmachines.co>
…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.
…e-key-leakage

Do not leak a private key that has a small typo
Signed-off-by: Jacinta Ferrant <jacinta@trustmachines.co>
Signed-off-by: Jacinta Ferrant <jacinta@trustmachines.co>
@Parikalp-Bhardwaj Parikalp-Bhardwaj requested a review from a team as a code owner October 21, 2024 12:21
@CLAassistant
Copy link

CLAassistant commented Oct 21, 2024

CLA assistant check
Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you all sign our Contributor License Agreement before we can accept your contribution.
8 out of 10 committers have signed the CLA.

✅ kantai
✅ obycode
✅ jcnelson
✅ saralab
✅ aldur
✅ wileyj
✅ Parikalp-Bhardwaj
✅ hstove
❌ jferrant
❌ zone117x
You have signed the CLA already but the status is still pending? Let us recheck it.

obycode
obycode previously approved these changes Oct 21, 2024
Copy link
Contributor

@obycode obycode left a 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!

@obycode obycode requested a review from a team October 21, 2024 13:07
@hstove
Copy link
Contributor

hstove commented Oct 21, 2024

Should we target this to develop instead of master?

@obycode
Copy link
Contributor

obycode commented Oct 21, 2024

Should we target this to develop instead of master?

Yes, good point.

@saralab
Copy link
Contributor

saralab commented Oct 21, 2024

@Parikalp-Bhardwaj : This should merge to develop instead of master before we can approve

@saralab saralab closed this Oct 21, 2024
@saralab saralab reopened this Oct 21, 2024
@obycode obycode requested a review from a team as a code owner October 21, 2024 20:29
@obycode
Copy link
Contributor

obycode commented Oct 21, 2024

Replaced with #5348

@obycode obycode closed this Oct 21, 2024
github-merge-queue bot pushed a commit that referenced this pull request Oct 23, 2024
Fix: Conditional logging for 'Proceeding to mine blocks' message #5338
@blockstack-devops
Copy link
Contributor

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.

@stacks-network stacks-network locked as resolved and limited conversation to collaborators Oct 30, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Node always logs "Proceeding to mine blocks" regardless of miner status