fix: add bounds checks for hard-coded slice index access#644
Merged
harp-intel merged 1 commit intomainfrom Feb 19, 2026
Merged
Conversation
Prevent index-out-of-range panics when functions receive empty or undersized data by adding early-return guards and per-iteration bounds checks to renderer and print functions. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Fields[0],Fields[1:],Fields[2:]) and cross-index mismatches where one field's values index into a shorter fieldslog.Errorwith table name and field count context before returningTest plan
make checkpasses (gofmt, go vet, staticcheck, golangci-lint, govulncheck, unit tests)make testpasses with no regressions🤖 Generated with Claude Code