-
Notifications
You must be signed in to change notification settings - Fork 472
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: runtime error: index out of range [-1] #2610
Comments
@williamdes: Thanks for opening an issue, it is currently awaiting triage. In the meantime, you can:
DetailsI am a bot created to help the crowdsecurity developers manage community feedback and contributions. You can check out my manifest file to understand my behavior and what I can do. If you want to use this for your project, you can check out the BirthdayResearch/oss-governance-bot repository. |
Thank you for concise replication instruction. Can confirm this happens on main branch, will spend sometime next week ironing it out. |
After the hub refactoring that was merged yesterday, master gives: FATA[2023-11-25 23:32:23] unable to load parser dump result: no parser found. Please install the appropriate parser and retry There is even a regression test. Is the message appropriate? |
For me it is not, it should say there is no input data. I think the message should be explicit about no data in the input or even in a file (does this make a crash too ?) |
Guess we could add a check to linecount crowdsec/cmd/crowdsec-cli/explain.go Lines 144 to 150 in 7c5cbef
If 0 return error as there is no content. This will work for logfile, log line and stdin. |
Merged fix, will be in 1.5.6 |
What happened?
What did you expect to happen?
No crash
How can we reproduce it (as minimally and precisely as possible)?
Anything else we need to know?
No response
Crowdsec version
OS version
No response
Enabled collections and parsers
No response
Acquisition config
No response
Config show
No response
Prometheus metrics
No response
Related custom configs versions (if applicable) : notification plugins, custom scenarios, parsers etc.
No response
The text was updated successfully, but these errors were encountered: