-
Notifications
You must be signed in to change notification settings - Fork 535
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 at completing block
log message
#967
Comments
I had memberlist configured, but due to the way the code is currently in
|
This is very likely related to #940. Will dig into it. |
Unable to reproduce. :/ Can you dump your version ^ like the first few lines of this snippet as well as mention which docker-compose you are using? |
Here is the full log for the tempo instance that crashed.
I've just committed the docker-compose I'm using here: https://github.com/zalegrala/tempo/tree/haOperationalRunMode/example/docker-compose/ha |
I met with the same situation ( commit: 3108978)
|
OK. Able to reproduce this error, its happening in the case where search is not enabled. I missed that. Will submit a patch soon. |
Thanks for reporting this @zalegrala, caught an evasive bug! |
Thanks for the fix @annanay25! |
Describe the bug
It appears that when a block is completing, we have an
index out of range
panic.To Reproduce
Steps to reproduce the behavior:
3108978d
configured with memberlist and s3 backend pointed to minioExpected behavior
Not panic.
Environment:
Additional Context
The text was updated successfully, but these errors were encountered: