-
Notifications
You must be signed in to change notification settings - Fork 140
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
Index out of range during expression eval #315
Comments
This issue also affects me, it happens from time to time and I see no chance to debug it.
|
Ack. This is on my stack, but there are higher-priority issues before it in line. |
@gunnihinn any news on this? May there be a fix in booking.com fork? |
Issue is quite old, since then there was a commit that should fix it: a94b484#diff-2ed1bb34a4e0bd489fb6a97a4300aede As when the issue was open, line 72 was:
So the panic with "index out of range" message might occur only if len(arg) == 0 and there is no arg[0], which was fixed by the commit I've referenced above. |
If you have a reproduction based on current master - please update the issue (likely it won't be possible to get this panic anymore). However I'd need at least following information:
|
Still noticing the same issue on current master @Civil
|
@cjagus it seems that your case is related to a different issue like #186 TLDR; carbonapi currently assume that all Metrics for the function will have same resolution, if they don't - it won't extrapolate or interpolate them as graphite-web do, and that likely causes your panic to appear. It's a long known issue, but different from the one that's discussed here. |
This should be obsolete and work better after #496 If this still happens with current master or newer, please open new bug with stacktraces and/or test cases. |
I see this error in
carbonapi.log
on one of our hosts:Stack trace:
This issue is mostly a reminder to myself to debug this further. The first step should be to recover from that panic and dump the data that's causing it to disk so we can stare at it.
The text was updated successfully, but these errors were encountered: