JakeWharton / JakeWharton/hugo
Take care if the arguments are too big!
- Dominant language
- Java
- Stars
- 7.9k
- Forks
- 792
- PR merge metrics
- No merged PRs in 30d
Description
I spent about half an hour debugging a particular part of my code later to realize it was the @DebugLog annotation that was causing the huge delay!
One of the arguments was a byte array (of an image, hence huge) and I suppose printing that to Logcat was the bottleneck. Shouldn't hugo *smartly* not print any argument that's just too huge? Or this could be a parameter (if it already isnt there!).
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by locating the @DebugLog argument-logging path and reproduce the delay with a very large byte-array argument sent to Logcat. Determine how oversized arguments should be handled or configured; done means large arguments no longer cause the reported logging bottleneck, with a regression check for this case.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- android, java
- Domain
- observability, performance
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100