Better error logging
Open
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 145
- Forks
- 3
- PR merge metrics
- No merged PRs in 30d
Description
It would be nice if the actual source code could get printed where the error happened.
Contributor guide
No contributing guide indexed for this repository
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
The issue names no file, test, or entry point. First identify how errors are currently logged and reproduce one failure; done should be defined as showing the relevant source code at the error location, with an example or test documenting the expected output.
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
- Needs clarification
- Newbie friendliness
- 25/100