always return with this error. ["There was an error loading the tables"]

[TrendTech]

1. i follow the install instruction
2. i add a mysql database.
3. when i try to visit the tables. it bring this error. i try old version. still the same
4. what i miss in my install process?

[novice-gamer]

I also encountered this problem

[GeorgeSpring]

I also encountered this problem

[TrendTech]

mysql version is 5.7
and even the example database is failed to fetch the table.

[mAd-DaWg]

Same issue here in the docker. It lists the tables fine, but when trying to select a table this error occurs. I noticed that its putting /undefined/false on the end of the request url. when removing it, it seems to load response json fine.

werkzeug.exceptions.NotFound: 404 Not Found: The requested URL was not found on the server. If you entered the URL manually please check your spelling and try again.
[15/Sep/2022:10:40:18 +0000] "GET /superset/tables/4/exampletable/undefined/false/ HTTP/1.1" 404 334 "http://0.0.0.0:8088/tablemodelview/list/?pageIndex=0&sortColumn=changed_on_delta_humanized&sortOrder=desc" "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/105.0.0.0 Safari/537.36"

Also saw a flask error on startup which may be relevant:
/usr/local/lib/python3.8/site-packages/flask_appbuilder/models/sqla/interface.py:68: SAWarning: relationship 'SqlaTable.slices' will copy column tables.id to column slices.datasource_id, which conflicts with relationship(s): 'Slice.table' (copies tables.id to slices.datasource_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="table"' to the 'SqlaTable.slices' relationship. (Background on this error at: https://sqlalche.me/e/14/qzyx)

[bumasl]

same error marks me, someone could already solve the error?

[C-monC]

Same issue, huge block currently

[andrearoota]

Same issue

[garystafford]

Same issue with the latest tag (3ed6d3e979351616cd5474b2404e136604d74cf50e4eeaf2e5a74f6f8a32130a).

[C-monC]

If you use superset in production and want to track the fix #21470

[bumasl]

Can someone explain me the detailed steps to solve this problem?
I thank you for your kind attention

[C-monC]

Pulling the latest version should work.
Make sure to clear cache.

[bumasl]

Thank you very much for your prompt response, in this order it worked for me
1 - delete container
docker-compose -f docker-compose-non-dev.yml down -v
2- clearing images from previous container
sudo docker system prune --all
3- Start the container again
docker-compose -f docker-compose-non-dev.yml up

I hope it helps those who have the same problem

[C-monC]

Try with docker-compose.yml - it should work.

[sjmillius]

I'm still seeing this issue in our setup on Google cloud.
We're using Postgres proxy to Cloud SQL, Redis and depoly via helm using apache/superset:latest.

It still produces the error in sqllab: [There was an error loading the tables] as described here.
How can this be resolved?