Implementation of a logger/error handler
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 25
- Forks
- 67
- Avg merge
- 3d 8h
- Merged PRs (30d)
- 2
Description
The existing error logging/handling method via the two mandatory CCPP arguments errmsg/ccpp_error_message and errflg/ccpp_error_flag should be replaced with a proper logger/error handler.
Ideally it would provide a call stack to where an error was generated and what the error is, and different logging levels (debug, info, warning, error, critical?).
Another nice-to-have would be to be able to redirect these log messages to separate log files or stdout/stderr or some other method that can be informed by the host model.
This is a post-capgen-unification task.
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
No files, tests, or entry points are named. Start by locating the current handling of the mandatory errmsg/ccpp_error_message and errflg/ccpp_error_flag arguments, then define the logger's call-stack reporting, logging levels, and host-controlled output destinations; done means these requirements are implemented and covered by tests.
Written by the indexing model from the issue text.
Assessment
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100