-
Notifications
You must be signed in to change notification settings - Fork 27
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
Dekart stop working with no error messages (deadlock) #25
Comments
Some example errors (with identifying data removed): googleapi: Error 403: Access Denied these errors caused the self-hosted website to crash. |
Hey @philipmargeotab will try to help you. I'm running Dekart instance on GCP for the Playground, so it should be possible. Can you please tell:
Also can you please set |
Version is 0.7 # https://cloud.google.com/appengine/docs/flexible/custom-runtimes/configuring-your-app-with-app-yaml#intro manual_scaling: resources: env_variables: beta_settings: ### |
Hey I think I did manage to reproduce problem, will keep you posted here |
I was able to reproduce dead lock here https://github.com/dekart-xyz/dekart/blob/v0.7.0/src/server/report/report.go#L36 |
Hey so I believe that problem was with a deadlock. In Dekart there is of course a lot error handling but deadlock formally is not an error. It's not easy to reproduce locally. I found few potential issues in the code and address them d4395ce @philipmargeotab could you pease update Dekart to |
Yes it appears to work now; no more deadlock. Thank you! |
Great! |
Fixed in |
Our team set up Dekart.xyz on our own GCP using the instructions provided in https://dekart.xyz/docs/self-hosting/app-engine/, using Google App Engine. However, an issue we are running into is - whenever we run an invalid query, no error message comes up (either in Dekart or in the docker logs), and we have to reset the docker image every time, and only then do we see the error message. Is there better error handling available that doesn't cause Dekart to crash every time we submit a query with syntax or permissions errors (e.g. a column doesn't exist, or a user doesn't have permission to a table). The crash also prevents users from returning to the home 'reports' screen. It goes completely blank.
The text was updated successfully, but these errors were encountered: