libgit2 / libgit2/libgit2sharp
Logging pollutes log messages of contained programs
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 3.5k
- Forks
- 925
- PR merge metrics
- No merged PRs in 30d
Description
You are opening a bug report against the LibGit2Sharp project: we
use GitHub Issues for tracking bug reports and feature requests. If
you have a question about an API or usage, please ask on StackOverflow:
http://stackoverflow.com/questions/tagged/libgit2sharp.
Otherwise, to report a bug, please fill out the reproduction steps
(below) and delete these introductory paragraphs. Thanks!
Reproduction steps
Set GlobalSettings.LogConfiguration
Pass log messages from libgit2sharp to your own logging solution
Expected behavior
Libgit2sharp does not send an unidentifiable Logging enabled at level logmessage that we cannot disable
Actual behavior
Libgit2sharp sends an unidentifiable Logging enabled at level logmessage that we cannot disable and which confuses our users because it is not the same loglevel name as they set in our app config.
Version of LibGit2Sharp (release number or SHA1)
Operating system(s) tested; .NET runtime tested
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.
Research direction
Start by tracing GlobalSettings.LogConfiguration to the source of the exact "Logging enabled at level" message. Verify how the message is emitted and whether the configured logging behavior can suppress or correctly identify it; done means contained programs no longer receive the unidentifiable message.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp
- Domain
- observability
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100