-
Notifications
You must be signed in to change notification settings - Fork 198
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 due to index out of range if a request came in too early #32
Comments
not sure if it's related to how early is the connection at all, it seems to crash as soon as it gets a connection. I applied #30 but it didn't work
|
Thanks for the bug report! Can you please check if #33 fixes the issue for you? |
#33 fixed the issue. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Could be related to #29 and #30
I have a server (gRPC, HTTP, and HTTPs) that is intended to run on Kubernetes, relevant code:
Having a pod health check setup as follows:
Given the
initialDelaySeconds=5
, I assume the server has no time to setup all of the matchers and:Changing
initialDelaySeconds
to 20 seconds solves the problem.The text was updated successfully, but these errors were encountered: