-
Notifications
You must be signed in to change notification settings - Fork 199
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
We just upgraded to version v1.19.0 and are getting panics from the client #161
Comments
Is this surfacing in your tests as well, or only in production? |
Only in production. |
Can you retrieve the data via aql? |
Can you clarify your question? We are using version 1.11 with no problems. So the data is retrievable. But we aren't able to retrieve the exact data which caused the panics, there is no indication what that data was in the panic. |
This answers my question, I was trying to establish if the data is malformed or not. Let me go through the changes since 1.11 and see if I can pin down the change that might have caused the panic. Will get back to you in a day or two. I assume the panic happens only occasionally and not on each request, is that correct? |
It took about 10 minutes running in production before the servers started crashing. |
This should have been taken care of in the latest release. |
We would like to update to 1.20 and would like a recent stable version to be able to upgrade from.
The text was updated successfully, but these errors were encountered: