-
Notifications
You must be signed in to change notification settings - Fork 3.6k
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: expected either int64 or float64, got... #4666
Labels
Comments
What was the query you were running? Also, do you have some sample data points? |
I encountered the same issue running influxdb-0.9.5-0.1.rc3.x86_64.rpm. Here is the query:
|
Hello, Crash occurred again.
Regards, |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hello,
I have a panic...
I also read some code :
https://github.com/influxdb/influxdb/blob/master/tsdb/raw.go from line 678 to line 708.
For what I understand, cur[1] and prev[1] can be anything until line 692. At line 708, we can assert that they are either int64 or float64.
It seems that you check the type of cur[1]. But not prev[1]. Not a problem because prev[1] is previous cur[1].
Except in one case : you never check the type of
results[0][1]
(e.g. prev[1] when i == 1 at first run of the loop)I guess that in my case result[0][1] is neither int64 nor float64, and then
int64toFloat64(prev[1])
will do strange things and panic.I have no idea if the fix is to just add a check for prev[1] when i == 1 or if this bug shows a bigger problem and needs more reengineering.
Regards,
Yves
The text was updated successfully, but these errors were encountered: