-
Notifications
You must be signed in to change notification settings - Fork 4.9k
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
Unable to add cards to dashboards or search for cards, StackOverflowError on backend #7223
Comments
We see a similar issue on opening /questions page and home page.
|
@kristian-elder @satyadeepk I believe I have a fix for the issue you're seeing. It would be immensely helpful if you could try it out and confirm the fix. Try PR #7245 (branch |
Fixed by #7245 |
Thanks @camsaul. I would like to try this fix. I am new to this and installed using docker on EC2. How do I build a branch using this setup? |
The really-really boiled down version: A hotfix branch build ... given you have the prerequisites installed already. The prerequisites are covered in: https://github.com/metabase/metabase/blob/master/docs/developers-guide.md#install-prerequisites |
Browser: Version 65.0.3325.146 (Official Build) (64-bit)
OS: Kubuntu 16 (client), official docker image (server)
Database: MySQL for both metabase itself and querying
Metabase version: Failing on 0.28.3, tried various others
Metabase hosting environment: Docker on Kubernetes in Google Cloud with official Docker images
Description of issue
Our Metabase instance is currently in a very unhappy state. I am unable to list or search for cards outside of a specific collection, and unable to add cards to dashboards.
When attempting to add a card to a dashboard, I see the following in the browser console:
Followed by - later on:
It appears that the response is:
.. and I see this entry in the server logs:
I'd appreciate any suggestions for how to work around this issue in the short term, fixing any potential offending card that triggers odd behaviours? We have been using Metabase for a while now so have gone through a number of past versions on the same instance.
The text was updated successfully, but these errors were encountered: