HappyMiner opened a new issue #11171: URL: https://github.com/apache/incubator-superset/issues/11171
A clear and concise description of what the bug is. ### Expected results Following the steps on: https://superset.apache.org/docs/installation/installing-superset-using-docker-compose I expect to be able to use superset after doing "docker-compose up" and logging in. ### Actual results I am able to login but only see a broken screen, displaying 3 items: - "x" button - "close" button - broken image picture #### Screenshots Please see attached screenshot. <img width="1919" alt="image" src="https://user-images.githubusercontent.com/11057169/95200837-9c056e80-0811-11eb-861a-974a083737fd.png";> #### How to reproduce the bug Follow instructions to install and run on MacOS as described in: https://superset.apache.org/docs/installation/installing-superset-using-docker-compose Login and find the broken page. ### Environment (please complete the following information): - superset version: `unknown` There is no version information anywhere to be found. I did "git clone https://github.com/apache/incubator-superset.git"; on TUE OCT 6th at around 08:27 New York time if that helps. - python version: `python --version`: Python 2.7.16 but Python 3.7.6 is also installed - node.js version: `node -v`: I do not have node installed. - npm version: `npm -v` No NPM on Mac. ### Checklist Make sure these boxes are checked before submitting your issue - thank you! - [ ] I have checked the superset logs for python stacktraces and included it here as text if there are any. WHERE to find these? - [X] I have reproduced the issue with at least the latest released version of superset. I tried to do `docker-compose build` AND `docker-compose up --build` to see if this could fix the issue. No change. - [X] I have checked the issue tracker for the same issue and I haven't found one similar. I have found one issue from 2019: https://github.com/apache/incubator-superset/issues/8818 But nothing in there seemed to help me. ### Additional context While I was typing this I saw the terminal showing additional information: "superset_node | npm WARN tarball tarball data for [email protected] (sha512-GUXpO713URNzaExVUgBtqA5fr2UuxUG/fVitI04zEFHVL2FHSjd672alHq8E16oQqRNzF0m1bmx8WlTnDrGSqQ==) seems to be corrupted. Trying one more time." I then scrolled up to check if there was more and got to: "superset_init | Init Step 4/4 [Starting] -- Loading examples" I did not find the related "[Complete]" tag however. Does this mean that there is still some kind of installation running in the background? If this is the case and the install is still running, why not tell the user clearly? Also why can I already open the URL if there is nothing there (yet)? Most likely something went wrong during the install and Step 4 never got completed I guess? The terminal gets flooded with "superset_app | INFO:werkzeug:127.0.0.1 - - [06/Oct/2020 12:34:25] "GET /health HTTP/1.1" 200 -" which to me looks like an "is_alive" response, telling me, as the unsuspecting user, that everything is done. ---------------------------------------------------------------- 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. For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
![https://user-images.githubusercontent.com/11057169/95200837-9c056e80-0811-11eb-861a-974a083737fd.png"](https://user-images.githubusercontent.com/11057169/95200837-9c056e80-0811-11eb-861a-974a083737fd.png"){kind=link}