Repository navigation
fix: resolve duplicated status parsing in ltsvreader - #120
Conversation
PR Reviewer Guide 🔍(Review updated until commit 0e7faa8)Here are some key observations to aid the review process:
✅ Resolved findingsjsonreader/jsonreader.go:73-75Malformed JSON A JSON parse error now returns values found before the error instead of discarding them. With status keys ltsvreader/ltsvreader.go:41-46Bitset Overflow For a configured key at index 64 or higher, this shift produces a zero bit. Repeated occurrences are then counted as new matches, so enough duplicates can make ltsvreader/ltsvreader.go:43-48Duplicate Tracking For configurations with at least 65 keys, shifting a |
Benchmark ComparisonBase: BenchmarkMainParse results |
…nd improve readability
|
Persistent review updated to latest commit c7049f8 |
…ng invalid states
|
|
Persistent review updated to latest commit 0e7faa8 |



PR Type
Bug fix, Enhancement
Description
Preserve first duplicate LTSV status value.
Prioritize configured status keys in both readers.
Return no values when parsing fails.
Replace parse flags with value checks.
File Walkthrough
2 files
Remove parse flags from the reader interfaceValidate parsed values instead of status flags3 files
Remove tests for obsolete parse flagsUpdate JSON tests for two-value parse resultsAdd duplicate-key coverage and update parse assertions1 files
Simplify JSON results and handle parse errors1 files
Ignore duplicate fields and prioritize configured statuses1 files
Declare additional build and check targets phony