mapbox / mapbox/mapbox-base-android
Split module loader exception logs if they exceed the buffer size
Open
Nobody has claimed this yet.
- Dominant language
- Kotlin
- Stars
- 12
- Forks
- 6
- PR merge metrics
- No merged PRs in 30d
Description
Sometimes the stack traces when we fail to load a module are long enough to not fit into a single log statement. This can result in truncating important information, like the cause of the `InvocationTargetException` which is typically at the bottom of the stack trace.
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 by locating the module loader's exception logging in this repository and reproduce a module-load failure with a stack trace longer than the log buffer. Verify that the complete trace, including the underlying InvocationTargetException cause, is emitted across multiple log statements without truncation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- android, kotlin
- Domain
- mobile
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100