JakeWharton / JakeWharton/hugo
flag methods w/ times > N msec as errors
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 7.9k
- Forks
- 792
- PR merge metrics
- No merged PRs in 30d
Description
E.g., during debug, I'd want to be able to flag methods that take "too long", e.g., DB access methods that take over 1sec and if that happens, put a msg in the log at a warning level.
So instead of @DebugLog, maybe add "@DebugLogSlug(1000)" for anything that goes over 1sec?
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 source files or tests are named. Start by reading the existing @DebugLog annotation and the method-call logging path, then determine how a time threshold and warning-level output should fit the current design. Done means calls exceeding a configured threshold are identified and logged as warnings, with coverage for the new behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- observability, tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100