paulvanharen opened a new issue, #23181: URL: https://github.com/apache/superset/issues/23181
After a clean install of the [release candidate 2.1.0RC01](https://github.com/apache/superset/discussions/23164), superset doesn't launch correctly. #### How to reproduce the bug #!/bin/bash # Clean up old installation rm -rf ~/.superset cd ~/workspace/IoT2 rm -rf superset2.1 # Extract new installation tar zxf ~/Downloads/apache-superset-2.1.0rc1-source.tar.gz mv apache-superset-2.1.0rc1/ superset2.1 cd superset2.1 # Create enviornment and install python3.10 -m venv venv . ./venv/bin/activate pip install --upgrade pip pip install . # Set up superset db upgrade export FLASK_APP=superset superset fab create-admin superset init # Run superset run -p 8088 --with-threads --reload --debugger ### Expected results No errors nor major warnings during installation. When launching the welcome page at http://localhost:8088/superset/welcome/, a clean formatted page. ### Actual results - `pip install .` is clean - `superset db upgrade` mentions that no PIL installation was found - furthermore `superset db upgrade` also warns > superset2.1/venv/lib/python3.10/site-packages/flask_appbuilder/models/sqla/interface.py:67: 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) - the same two warnings are raised during the `superset fab create-admin` and again for `superset init` - `superset run` gives again the same warning - Cleaning the browser cache and then loading the local superset welcome page yields a broken page - see screenshot - Furthermore, in the superset run log it is found that loading.gif is not found (HTTP 404). #### Screenshots If applicable, add screenshots to help explain your problem. ### Environment - browser type and version: Brave - latest version - superset version: 2.1.0rc1 - python version: 3.9.16 as well as 3.10.6 - node.js version: v12.22.9 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: notifications-unsubscr...@superset.apache.org.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: notifications-unsubscr...@superset.apache.org For additional commands, e-mail: notifications-h...@superset.apache.org
