-
Notifications
You must be signed in to change notification settings - Fork 53
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Panic, slice index out of bounds #20
Comments
Would you mind sharing a rule file it fails on? |
I had to bisect all the rules (hard to know which one it's reporting on) but this one makes it fail consistently. Please note theres an empty line at the end
|
Just changing this 4 lines work:
But probably should be fixed on the line detection code. You can reduce the test case to having a single alert and being the last one like this:
|
Thanks! Can you share your pint config too? |
Sure!
It's basically a copy of the one available as an example. |
It looks like escaped new lines in |
interesting, i think the warning is a good option. When do you think you'd emit this warning? Whenever you see a newline on the text? Or when there's a mismatch with the line count ? |
When we try to read more lines then the source file has |
Added a workaround for now, need to address the root issue |
I just got this panic:
on this line:
pint/internal/reporter/console.go
Line 71 in 452a61c
Seems like the check can fail sometimes
The text was updated successfully, but these errors were encountered: