Log formatting + improvements
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 25/100
Research direction
No files, tests, or entry points are named. Start by locating the code responsible for log formatting and command execution, then define the expected readable step output and captured stdout/stderr before making changes; done means all three listed task areas are addressed and verified.
Written by the indexing model from the issue text.
Description
### Tasks
- [ ] Formatting improvements. Right now the formatting for the logs make the log messages too dense and hard to visually parse.
- [ ] Capturing the std out & err from command execution within the logs.
- [ ] Better formatting for listing out the steps that will be executed within the logs
- Dominant language
- Go
- Stars
- 40
- Forks
- 27
- PR merge metrics
- No merged PRs in 30d
Getting set up
- Ships a Dockerfile or Docker Compose file
- No pull request template
- Read the contributing 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 Azure/InnovationEngine
-
Azure/InnovationEngine#262 · 1 reaction · 1 assignee ·
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
Azure/InnovationEngine#259 ·
-
bug enhancement
Difficulty 3/5 1-2 days Newbie friendliness 38/100
Azure/InnovationEngine#258 ·
-
enhancement innovation engine
Azure/InnovationEngine#256 · 1 reaction · 1 assignee ·
-
Difficulty 1/5 Under an hour Newbie friendliness 55/100
Azure/InnovationEngine#252 · 1 comment ·
All issues in Azure/InnovationEngine
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
google/differential-privacy#516 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 90/100
lightninglabs/lndmon#140 ·
-
documentation good first issue ready-for-triage ready-to-code
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
release-engineering/fbc-update-planner#102 · 3 comments ·
Maintainers usually reply within 5 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
yetone/magpie#562 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
Maintainers usually reply within 4 days