[FEAT] - use log_info for the chain syncing messages
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 45/100
Research direction
Locate the chain syncing messages and the printf calls that write them to the terminal, then inspect existing log_info usage in the project. Done means the sync messages use log_info and no longer break stdout consistency.
Written by the indexing model from the issue text.
Description
Describe the Problem
using printf to print to terminal, breaking the consistency of the stdout
Describe the Solution
use log_info for printing sync messages
Optional Additional Details
No response
- Dominant language
- Shell
- Stars
- 7
- Forks
- 0
- Avg merge
- 2h 38m
- Merged PRs (30d)
- 30
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from bitcoin-tools/nodebuilder
-
feature
Difficulty 3/5 1-2 days Newbie friendliness 20/100
bitcoin-tools/nodebuilder#2588 ·
-
bug
Difficulty 4/5 3-5 days Newbie friendliness 25/100
bitcoin-tools/nodebuilder#2587 ·
-
feature
Difficulty 2/5 1-3 hours Newbie friendliness 45/100
bitcoin-tools/nodebuilder#2580 ·
-
feature
Difficulty 4/5 3-5 days Newbie friendliness 15/100
bitcoin-tools/nodebuilder#2578 ·
-
feature
Difficulty 4/5 3-5 days Newbie friendliness 45/100
bitcoin-tools/nodebuilder#2552 ·
All issues in bitcoin-tools/nodebuilder
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
astral-sh/python-build-standalone#1293 ·
-
package-update
Difficulty 1/5 Under an hour Newbie friendliness 90/100
oSoWoSo/vOid_Community_repOsitory#185 · 1 comment ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
carbon-language/carbon-lang#7821 ·