mlcommons / mlcommons/inference
Update logging to use color logging and loguru
Open
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 1.6k
- Forks
- 650
- Avg merge
- 1d 22h
- Merged PRs (30d)
- 6
Description
The submission checker currently emits plain-text logs, making it difficult for users to quickly distinguish between informational messages and actionable issues. Log levels such as INFO, DEBUG, WARNING, ERROR, and CRITICAL appear identical in formatting, which reduces readability and slows down debugging.
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 at the submission checker and locate its logging setup and entry points. Check how INFO, DEBUG, WARNING, ERROR, and CRITICAL are currently emitted; the work is done when the checker uses loguru and color formatting makes these levels distinguishable.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100