NullPointerException and formatting termination if at least one corpus file have one or more parsing errors
Open
bug
- Dominant language
- Java
- Stars
- 477
- Forks
- 84
- PR merge metrics
- No merged PRs in 30d
Description
Corpus files with errors or parsing errors should be ignored somehow.
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by reproducing the failure with a corpus file containing parsing errors, then trace the resulting NullPointerException and formatting termination through the corpus-processing entry point. Done means erroneous corpus files are ignored and processing continues for files without parsing errors, without terminating formatting.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- data
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100