crossbario / crossbario/autobahn-python
Audit all logging calls
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 2.5k
- Forks
- 768
- PR merge metrics
- No merged PRs in 30d
Description
See https://github.com/crossbario/txaio/issues/60
There are still places where the loggers aren't using the "new-logger" style correctly -- and will end up producing formatting exceptions in some cases (i.e. cases where the "format" string contains embedded {}'s).
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 reviewing the repository-wide logging calls and the referenced txaio issue 60 to identify the expected "new-logger" style. The issue names no files or tests, so trace each logging call and verify that format strings containing embedded {} no longer produce formatting exceptions. Done means the remaining logging calls consistently use the expected style.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- observability-sre
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100