Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Can't log in using 0.36.0rc3 #9457

Closed
francishemingway opened this issue Apr 2, 2020 · 5 comments
Closed

Can't log in using 0.36.0rc3 #9457

francishemingway opened this issue Apr 2, 2020 · 5 comments

Comments

@francishemingway
Copy link
Contributor

francishemingway commented Apr 2, 2020 •
edited
Loading

A clear and concise description of what the bug is.

Expected results

I'm able to log in.

Actual results

Login page comes up, I enter my credentials.
login
I just see a spinner and it never goes anywhere.
spinner

How to reproduce the bug

Log in using credentials.

To install, I followed the instructions listed here: https://superset.incubator.apache.org/installation.html#superset-installation-and-initialization

with one exception in that I ran
pip install https://dist.apache.org/repos/dist/dev/incubator/superset/0.36.0rc3/apache-superset-incubating-0.36.0rc3-source.tar.gz

Environment

  • superset version: 0.36.0
  • python version: 3.8.2
  • node.js version: v13.12.0
  • npm version: 6.14.4

Checklist

Make sure these boxes are checked before submitting your issue - thank you!

  • [x ] I have checked the superset logs for python stacktraces and included it here as text if there are any.
  • [ x] I have reproduced the issue with at least the latest released version of superset.
  • [ x] I have checked the issue tracker for the same issue and I haven't found one similar.

Additional context

Here's the output when I run Superset:

(venv) [francis@localhost ~]$ superset run -p 8088 --with-threads --reload --debugger -h 0.0.0.0 logging was configured successfully
INFO:superset.utils.logging_configurator:logging was configured successfully
/home/francis/venv/lib64/python3.8/site-packages/flask_caching/init.py:188: UserWarning: Flask-Caching: CACHE_TYPE is set to null, caching is effectively disabled.
warnings.warn(

  • Serving Flask app "superset" (lazy loading)
  • Environment: production
    WARNING: This is a development server. Do not use it in a production deployment.
    Use a production WSGI server instead.
  • Debug mode: off
    INFO:werkzeug: * Running on http://0.0.0.0:8088/ (Press CTRL+C to quit)
    INFO:werkzeug: * Restarting with stat
    logging was configured successfully
    INFO:superset.utils.logging_configurator:logging was configured successfully
    /home/francis/venv/lib64/python3.8/site-packages/flask_caching/init.py:188: UserWarning: Flask-Caching: CACHE_TYPE is set to null, caching is effectively disabled.
    warnings.warn(
    WARNING:werkzeug: * Debugger is active!
    INFO:werkzeug: * Debugger PIN: 144-298-740
    INFO:werkzeug:10.0.2.2 - - [02/Apr/2020 17:59:43] "GET / HTTP/1.1" 302 -
    INFO:werkzeug:10.0.2.2 - - [02/Apr/2020 17:59:43] "GET /superset/welcome HTTP/1.1" 200 -
    INFO:werkzeug:10.0.2.2 - - [02/Apr/2020 17:59:53] "GET / HTTP/1.1" 302 -
    INFO:werkzeug:10.0.2.2 - - [02/Apr/2020 17:59:53] "GET /superset/welcome HTTP/1.1" 302 -
    INFO:werkzeug:10.0.2.2 - - [02/Apr/2020 17:59:53] "GET /login/ HTTP/1.1" 200 -
    INFO:werkzeug:10.0.2.2 - - [02/Apr/2020 17:59:53] "GET /static/appbuilder/css/font-awesome.min.css HTTP/1.1" 200 -
    INFO:werkzeug:10.0.2.2 - - [02/Apr/2020 17:59:53] "GET /static/appbuilder/css/bootstrap.min.css HTTP/1.1" 200 -
    INFO:werkzeug:10.0.2.2 - - [02/Apr/2020 17:59:53] "GET /static/appbuilder/datepicker/bootstrap-datepicker.css HTTP/1.1" 200 -
    INFO:werkzeug:10.0.2.2 - - [02/Apr/2020 17:59:53] "GET /static/appbuilder/select2/select2.css HTTP/1.1" 200 -
    INFO:werkzeug:10.0.2.2 - - [02/Apr/2020 17:59:53] "GET /static/appbuilder/css/ab.css HTTP/1.1" 200 -
    INFO:werkzeug:10.0.2.2 - - [02/Apr/2020 17:59:53] "GET /static/appbuilder/css/flags/flags16.css HTTP/1.1" 200 -
    INFO:werkzeug:10.0.2.2 - - [02/Apr/2020 17:59:53] "GET /static/appbuilder/js/ab_filters.js HTTP/1.1" 200 -
    INFO:werkzeug:10.0.2.2 - - [02/Apr/2020 17:59:53] "GET /static/appbuilder/js/ab_actions.js HTTP/1.1" 200 -
    INFO:werkzeug:10.0.2.2 - - [02/Apr/2020 17:59:53] "GET /static/appbuilder/js/jquery-latest.js HTTP/1.1" 200 -
    INFO:werkzeug:10.0.2.2 - - [02/Apr/2020 17:59:53] "GET /static/appbuilder/js/bootstrap.min.js HTTP/1.1" 200 -
    INFO:werkzeug:10.0.2.2 - - [02/Apr/2020 17:59:53] "GET /static/appbuilder/datepicker/bootstrap-datepicker.js HTTP/1.1" 200 -
    INFO:werkzeug:10.0.2.2 - - [02/Apr/2020 17:59:53] "GET /static/appbuilder/js/ab.js HTTP/1.1" 200 -
    INFO:werkzeug:10.0.2.2 - - [02/Apr/2020 17:59:53] "GET /static/assets/images/superset-logo@2x.png HTTP/1.1" 404 -
    INFO:werkzeug:10.0.2.2 - - [02/Apr/2020 17:59:53] "GET /static/appbuilder/fonts/fontawesome-webfont.woff2?v=4.7.0 HTTP/1.1" 200 -
    INFO:werkzeug:10.0.2.2 - - [02/Apr/2020 17:59:53] "GET /static/appbuilder/img/flags/flags16.png HTTP/1.1" 200 -
    INFO:werkzeug:10.0.2.2 - - [02/Apr/2020 17:59:53] "GET /static/appbuilder/select2/select2.js HTTP/1.1" 200 -
    INFO:werkzeug:10.0.2.2 - - [02/Apr/2020 17:59:54] "GET /static/assets/images/favicon.png HTTP/1.1" 404 -
    INFO:werkzeug:10.0.2.2 - - [02/Apr/2020 18:00:57] "GET /superset/ HTTP/1.1" 404 -
    INFO:werkzeug:10.0.2.2 - - [02/Apr/2020 18:00:57] "GET /favicon.ico HTTP/1.1" 404 -
    INFO:werkzeug:10.0.2.2 - - [02/Apr/2020 18:00:59] "GET / HTTP/1.1" 302 -
    INFO:werkzeug:10.0.2.2 - - [02/Apr/2020 18:00:59] "GET /superset/welcome HTTP/1.1" 200 -
@francishemingway
Copy link
Contributor Author

@villebro I tested the latest release candidate and I got stuck here.

@villebro
Copy link
Member

villebro commented Apr 3, 2020

@francishemingway You should not be using Node 13, please downgrade to Node 12. Can you see if that solves it? If so I'll add that to the docs! Alternatively, feel free to put through a PR 🙂

@villebro villebro mentioned this issue Apr 3, 2020
Closed
@narendrans
Copy link
Contributor

I faced the same issue and Node 12 makes it to work. I can confirm it.

@liangsieng
Copy link

I have downgraded to Node 12 but still facing the same issue.

Node version: v12.16.1

logging was configured successfully
INFO:superset.utils.logging_configurator:logging was configured successfully
/data/superset/lib64/python3.6/site-packages/flask_caching/__init__.py:189: UserWarning: Flask-Caching: CACHE_TYPE is set to null, caching is effectively disabled.
  "Flask-Caching: CACHE_TYPE is set to null, "
 * Environment: production
   WARNING: This is a development server. Do not use it in a production deployment.
   Use a production WSGI server instead.
 * Debug mode: off
INFO:werkzeug: * Running on http://0.0.0.0:8080/ (Press CTRL+C to quit)
INFO:werkzeug: * Restarting with stat
logging was configured successfully
INFO:superset.utils.logging_configurator:logging was configured successfully
/data/superset/lib64/python3.6/site-packages/flask_caching/__init__.py:189: UserWarning: Flask-Caching: CACHE_TYPE is set to null, caching is effectively disabled.
  "Flask-Caching: CACHE_TYPE is set to null, "
WARNING:werkzeug: * Debugger is active!
INFO:werkzeug: * Debugger PIN: 234-768-526
INFO:werkzeug:192.168.1.1 - - [06/Apr/2020 18:02:28] "GET / HTTP/1.1" 302 -
INFO:werkzeug:192.168.1.1 - - [06/Apr/2020 18:02:28] "GET /superset/welcome HTTP/1.1" 302 -
INFO:werkzeug:192.168.1.1 - - [06/Apr/2020 18:02:28] "GET /login/ HTTP/1.1" 200 -
INFO:werkzeug:192.168.1.1 - - [06/Apr/2020 18:02:37] "POST /login/ HTTP/1.1" 302 -
INFO:werkzeug:192.168.1.1 - - [06/Apr/2020 18:02:37] "GET / HTTP/1.1" 302 -
INFO:werkzeug:192.168.1.1 - - [06/Apr/2020 18:02:38] "GET /superset/welcome HTTP/1.1" 200 -
INFO:werkzeug:192.168.1.1 - - [06/Apr/2020 18:03:49] "GET /superset/welcome HTTP/1.1" 200 -

@francishemingway
Copy link
Contributor Author

Yes, it didn't work for my either to downgrade to Node 12. I think it was something to do with the building of the frontend assets as. I will close and reopen if I have a problem with the final release.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@narendrans @villebro @liangsieng @francishemingway