SetLogLevel defaultLevel not protected by mutex on wildcard case
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 25/100
Research direction
Start by reviewing pull request #188, which contains the proposed mutex protection and concurrency test. Run the test with the race detector to reproduce the previous failure; done means the wildcard case is race-free and the concurrency test passes.
Written by the indexing model from the issue text.
Description
I opened this PR (https://github.com/ipfs/go-log/pull/188) with an extra mutex protection for defaultLevel on wildcard case.
Also added a concurrency test that fails with the previous version when running with -race flag.
This was observed after upgrading our dependencies.
- 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 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
-
Non-blocking loggingOpenkind/enhancement
Difficulty 4/5 3-5 days 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