openframeworks / openframeworks/openFrameworks
Lessen confusion about fatal-level messages in logging example.
Open
Nobody has claimed this yet.
bitesize
example
feature
prelim-analysis
- Dominant language
- C++
- Stars
- 10.4k
- Forks
- 2.6k
- Avg merge
- 1d 21h
- Merged PRs (30d)
- 9
Description
Running loggingExample, on:
- Win8 x64
- VS2012 compilation
Output:
[ fatal ] New log level is verbose
[ fatal ] New log level is notice
[notice ] 5s timer: Run time is 35
[ fatal ] New log level is verbose
[ fatal ] New log level is notice
Reproduction:
Press v few times
This is normal?
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 with examples/utils/loggingExample/src/ofApp.cpp at the linked line and reproduce the output by pressing v several times in loggingExample. Check how the displayed log levels are selected and determine what wording would make the fatal-level messages less confusing. Done means the repeated level-change output is no longer misleading on the reported setup.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- observability-sre
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100