Non-blocking logging
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 35/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- go
- Domain
- observability-sre
Research direction
Start by locating the default zap file backend and tracing how it writes log messages. Implement bounded buffering that drops messages when full without blocking execution, then verify the backend's write and overflow behavior with the relevant tests or a focused reproduction.
Written by the indexing model from the issue text.
Description
The default zap file backend logging backend is really dumb and doesn't have any internal buffering. We need to:
- Buffer writes.
- Drop log messages when the buffer is full instead of blocking.
We should never block execution on logging.
- Dominant language
- Go
- Stars
- 63
- Forks
- 55
- PR merge metrics
- No merged PRs in 30d
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
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 ipfs/go-log
-
need/triage
Difficulty 2/5 1-3 hours Newbie friendliness 25/100
-
need/triage
Difficulty 3/5 1-2 days Newbie friendliness 52/100
-
exp/intermediate help wanted kind/enhancement
Difficulty 5/5 Over a week Newbie friendliness 35/100
-
Inconsistent APIOpen
Difficulty 5/5 Over a week Newbie friendliness 25/100
-
exp/novice help wanted P3
Difficulty 3/5 1-2 days Newbie friendliness 30/100
Similar issues
-
affects-8.5 component/session severity/moderate sig/transaction type/bug
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 1 day
-
enhancement good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
harvester/harvester#12311 · 1 comment ·
Maintainers usually reply within 1 day
-
verifyrun --bracket-digest --credit: relative --witness is could-not-check, absolute path creditsOpenbug effort:s impact:low raised-by:desk risk:low
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
medici-finance/assay#6580 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 80/100
blinklabs-io/gouroboros#3026 ·
Maintainers usually reply within 1 day