Issue 1:
superset version: 0.36.rc3

python version: 3.7.7

node.js version: 13.12.0

npm version: 6.14.4

F:\superset-dev\superset-frontend>npm run prod

superset@0.36.0 prod F:\superset-dev\superset-frontend

node --max_old_space_size=4096 ./node_modules/webpack/bin/webpack.js --mode=production --colors --progress

Starting type checking service...

Using 1 worker with 2048MB memory limit

591 modules

ERROR in ./src/SqlLab/index.jsx 23:16

Module parse failed: Unexpected token (23:16)

You may need an appropriate loader to handle this file type, currently no loaders are configured to process this file. See https://webpack.js.org/concepts#loaders

| import App from './App';

|

ReactDOM.render(, document.getElementById('app'));

|

ERROR in ./src/welcome/index.jsx 23:16

Module parse failed: Unexpected token (23:16)

You may need an appropriate loader to handle this file type, currently no loaders are configured to process this file. See https://webpack.js.org/concepts#loaders

| import App from './App';

|

ReactDOM.render(, document.getElementById('app'));

|

ERROR in ./src/profile/index.jsx 23:16

Module parse failed: Unexpected token (23:16)

You may need an appropriate loader to handle this file type, currently no loaders are configured to process this file. See https://webpack.js.org/concepts#loaders

| import App from './App';

|

ReactDOM.render(, document.getElementById('app'));

|

ERROR in ./src/addSlice/index.jsx 23:16

Module parse failed: Unexpected token (23:16)

You may need an appropriate loader to handle this file type, currently no loaders are configured to process this file. See https://webpack.js.org/concepts#loaders

| import App from './App';

|

ReactDOM.render(, document.getElementById('js-add-slice-container'));

|

ERROR in ./src/showSavedQuery/index.jsx 39:4

Module parse failed: Unexpected token (39:4)

You may need an appropriate loader to handle this file type, currently no loaders are configured to process this file. See https://webpack.js.org/concepts#loaders

|

| ReactDom.render(

<div>

| <Form

| schema={config.JSONSCHEMA}

ERROR in ./src/dashboard/index.jsx 42:16

Module parse failed: Unexpected token (42:16)

You may need an appropriate loader to handle this file type, currently no loaders are configured to process this file. See https://webpack.js.org/concepts#loaders

| );

|

ReactDOM.render(, document.getElementById('app'));

|

ERROR in ./src/explore/index.jsx 44:16

Module parse failed: Unexpected token (44:16)

You may need an appropriate loader to handle this file type, currently no loaders are configured to process this file. See https://webpack.js.org/concepts#loaders

| );

|

ReactDOM.render(, document.getElementById('app'));

|

npm ERR! code ELIFECYCLE

npm ERR! errno 2

npm ERR! superset@0.36.0 prod: node --max_old_space_size=4096 ./node_modules/webpack/bin/webpack.js --mode=production --colors --progress

npm ERR! Exit status 2

npm ERR!

npm ERR! Failed at the superset@0.36.0 prod script.

npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

npm ERR! A complete log of this run can be found in:

npm ERR! C:\Users\Administrator\AppData\Roaming\npm-cache_logs\2020-04-02T10_02_26_178Z-debug.log

Issue 2:
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.

I just see a spinner and it never goes anywhere.

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 -