You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@superset.apache.org by GitBox <gi...@apache.org> on 2022/07/18 14:51:51 UTC
[GitHub] [superset] LyZane opened a new issue, #20744: docker-compose up failed
LyZane opened a new issue, #20744:
URL: https://github.com/apache/superset/issues/20744
#### How to reproduce the bug
```bash
git clone https://github.com/apache/superset.git
cd superset
docker-compose -f docker-compose-non-dev.yml pull
docker-compose -f docker-compose-non-dev.yml up
```
### Expected results
visit: http://localhost:8088/ and http://localhost:8080/
<img width="694" alt="image" src="https://user-images.githubusercontent.com/1787721/179537491-eec1cbba-65c2-47c8-b0dd-74c6c7b79d5d.png">
### Environment
- browser type and version: Chrome 103.0.5060.114
- superset version: `2.0 (Tue Jun 28 08:53:02 2022 -0400)`
### Additional context
```log
$ docker-compose -f docker-compose-non-dev.yml up
Starting superset_cache ... done
Starting superset_db ... done
Starting superset_init ... done
Starting superset_app ... done
Starting superset_worker ... done
Starting superset_worker_beat ... done
Attaching to superset_db, superset_cache, superset_worker_beat, superset_worker, superset_app, superset_init
superset_app | Skipping local overrides
superset_app | Starting web app...
superset_cache | 1:C 18 Jul 2022 14:33:50.007 # oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo
superset_cache | 1:C 18 Jul 2022 14:33:50.008 # Redis version=7.0.3, bits=64, commit=00000000, modified=0, pid=1, just started
superset_cache | 1:C 18 Jul 2022 14:33:50.008 # Warning: no config file specified, using the default config. In order to specify a config file use redis-server /path/to/redis.conf
superset_cache | 1:M 18 Jul 2022 14:33:50.008 * monotonic clock: POSIX clock_gettime
superset_cache | 1:M 18 Jul 2022 14:33:50.009 * Running mode=standalone, port=6379.
superset_cache | 1:M 18 Jul 2022 14:33:50.009 # Server initialized
superset_cache | 1:M 18 Jul 2022 14:33:50.010 * Loading RDB produced by version 7.0.3
superset_cache | 1:M 18 Jul 2022 14:33:50.011 * RDB age 10 seconds
superset_cache | 1:M 18 Jul 2022 14:33:50.011 * RDB memory usage when created 1.19 Mb
superset_cache | 1:M 18 Jul 2022 14:33:50.011 * Done loading RDB, keys loaded: 11, keys expired: 0.
superset_cache | 1:M 18 Jul 2022 14:33:50.011 * DB loaded from disk: 0.000 seconds
db_1 |
db_1 | PostgreSQL Database directory appears to contain a database; Skipping initialization
db_1 |
superset_cache | 1:M 18 Jul 2022 14:33:50.011 * Ready to accept connections
db_1 | 2022-07-18 14:33:50.078 UTC [1] LOG: listening on IPv4 address "0.0.0.0", port 5432
db_1 | 2022-07-18 14:33:50.078 UTC [1] LOG: listening on IPv6 address "::", port 5432
superset_worker | Skipping local overrides
superset_worker | Starting Celery worker...
db_1 | 2022-07-18 14:33:50.086 UTC [1] LOG: listening on Unix socket "/var/run/postgresql/.s.PGSQL.5432"
db_1 | 2022-07-18 14:33:50.101 UTC [25] LOG: database system was shut down at 2022-07-18 14:33:40 UTC
superset_worker_beat | Skipping local overrides
superset_worker_beat | Starting Celery beat...
db_1 | 2022-07-18 14:33:50.189 UTC [1] LOG: database system is ready to accept connections
superset_init | Skipping local overrides
superset_init |
superset_init | ######################################################################
superset_init |
superset_init |
superset_init | Init Step 1/4 [Starting] -- Applying DB migrations
superset_init |
superset_init |
superset_init | ######################################################################
superset_init |
superset_app | usage: gunicorn [OPTIONS] [APP_MODULE]
superset_app | gunicorn: error: argument --max-requests: expected one argument
superset_app | Skipping local overrides
superset_app | Starting web app...
superset_app | usage: gunicorn [OPTIONS] [APP_MODULE]
superset_app | gunicorn: error: argument --max-requests: expected one argument
superset_app exited with code 2
superset_app | Skipping local overrides
superset_app | Starting web app...
superset_app | usage: gunicorn [OPTIONS] [APP_MODULE]
superset_app | gunicorn: error: argument --max-requests: expected one argument
superset_app exited with code 2
superset_app | Skipping local overrides
superset_app | Starting web app...
superset_app | usage: gunicorn [OPTIONS] [APP_MODULE]
superset_app | gunicorn: error: argument --max-requests: expected one argument
superset_app exited with code 2
superset_app | Skipping local overrides
superset_app | Starting web app...
superset_worker_beat | --------------------------------------------------------------------------------
superset_worker_beat | WARNING
superset_worker_beat | --------------------------------------------------------------------------------
superset_worker_beat | A Default SECRET_KEY was detected, please use superset_config.py to override it.
superset_worker_beat | Use a strong complex alphanumeric string and use a tool to help you generate
superset_worker_beat | a sufficiently random sequence, ex: openssl rand -base64 42
superset_worker_beat | --------------------------------------------------------------------------------
superset_worker_beat | --------------------------------------------------------------------------------
superset_worker_beat | logging was configured successfully
superset_worker_beat | 2022-07-18 14:34:05,223:INFO:superset.utils.logging_configurator:logging was configured successfully
superset_worker_beat | 2022-07-18 14:34:05,238:INFO:root:Configured event logger of type <class 'superset.utils.log.DBEventLogger'>
superset_worker | --------------------------------------------------------------------------------
superset_worker | WARNING
superset_worker | --------------------------------------------------------------------------------
superset_worker | A Default SECRET_KEY was detected, please use superset_config.py to override it.
superset_worker | Use a strong complex alphanumeric string and use a tool to help you generate
superset_worker | a sufficiently random sequence, ex: openssl rand -base64 42
superset_worker | --------------------------------------------------------------------------------
superset_worker | --------------------------------------------------------------------------------
superset_worker | logging was configured successfully
superset_worker | 2022-07-18 14:34:05,261:INFO:superset.utils.logging_configurator:logging was configured successfully
superset_worker_beat | Falling back to the built-in cache, that stores data in the metadata database, for the following cache: `FILTER_STATE_CACHE_CONFIG`. It is recommended to use `RedisCache`, `MemcachedCache` or another dedicated caching backend for production deployments
superset_worker_beat | 2022-07-18 14:34:05,264:WARNING:superset.utils.cache_manager:Falling back to the built-in cache, that stores data in the metadata database, for the following cache: `FILTER_STATE_CACHE_CONFIG`. It is recommended to use `RedisCache`, `MemcachedCache` or another dedicated caching backend for production deployments
superset_worker | 2022-07-18 14:34:05,274:INFO:root:Configured event logger of type <class 'superset.utils.log.DBEventLogger'>
superset_worker_beat | Falling back to the built-in cache, that stores data in the metadata database, for the following cache: `EXPLORE_FORM_DATA_CACHE_CONFIG`. It is recommended to use `RedisCache`, `MemcachedCache` or another dedicated caching backend for production deployments
superset_worker_beat | 2022-07-18 14:34:05,282:WARNING:superset.utils.cache_manager:Falling back to the built-in cache, that stores data in the metadata database, for the following cache: `EXPLORE_FORM_DATA_CACHE_CONFIG`. It is recommended to use `RedisCache`, `MemcachedCache` or another dedicated caching backend for production deployments
superset_worker | Falling back to the built-in cache, that stores data in the metadata database, for the following cache: `FILTER_STATE_CACHE_CONFIG`. It is recommended to use `RedisCache`, `MemcachedCache` or another dedicated caching backend for production deployments
superset_worker | 2022-07-18 14:34:05,289:WARNING:superset.utils.cache_manager:Falling back to the built-in cache, that stores data in the metadata database, for the following cache: `FILTER_STATE_CACHE_CONFIG`. It is recommended to use `RedisCache`, `MemcachedCache` or another dedicated caching backend for production deployments
superset_worker | Falling back to the built-in cache, that stores data in the metadata database, for the following cache: `EXPLORE_FORM_DATA_CACHE_CONFIG`. It is recommended to use `RedisCache`, `MemcachedCache` or another dedicated caching backend for production deployments
superset_worker | 2022-07-18 14:34:05,306:WARNING:superset.utils.cache_manager:Falling back to the built-in cache, that stores data in the metadata database, for the following cache: `EXPLORE_FORM_DATA_CACHE_CONFIG`. It is recommended to use `RedisCache`, `MemcachedCache` or another dedicated caching backend for production deployments
superset_app | usage: gunicorn [OPTIONS] [APP_MODULE]
superset_app | gunicorn: error: argument --max-requests: expected one argument
superset_app exited with code 2
superset_app | Skipping local overrides
superset_app | Starting web app...
superset_app | usage: gunicorn [OPTIONS] [APP_MODULE]
superset_app | gunicorn: error: argument --max-requests: expected one argument
superset_app exited with code 2
superset_init | --------------------------------------------------------------------------------
superset_init | WARNING
superset_init | --------------------------------------------------------------------------------
superset_init | A Default SECRET_KEY was detected, please use superset_config.py to override it.
superset_init | Use a strong complex alphanumeric string and use a tool to help you generate
superset_init | a sufficiently random sequence, ex: openssl rand -base64 42
superset_init | --------------------------------------------------------------------------------
superset_init | --------------------------------------------------------------------------------
superset_init | logging was configured successfully
superset_init | 2022-07-18 14:34:09,697:INFO:superset.utils.logging_configurator:logging was configured successfully
superset_init | 2022-07-18 14:34:09,730:INFO:root:Configured event logger of type <class 'superset.utils.log.DBEventLogger'>
superset_init | Falling back to the built-in cache, that stores data in the metadata database, for the following cache: `FILTER_STATE_CACHE_CONFIG`. It is recommended to use `RedisCache`, `MemcachedCache` or another dedicated caching backend for production deployments
superset_init | 2022-07-18 14:34:09,746:WARNING:superset.utils.cache_manager:Falling back to the built-in cache, that stores data in the metadata database, for the following cache: `FILTER_STATE_CACHE_CONFIG`. It is recommended to use `RedisCache`, `MemcachedCache` or another dedicated caching backend for production deployments
superset_init | Falling back to the built-in cache, that stores data in the metadata database, for the following cache: `EXPLORE_FORM_DATA_CACHE_CONFIG`. It is recommended to use `RedisCache`, `MemcachedCache` or another dedicated caching backend for production deployments
superset_init | 2022-07-18 14:34:09,764:WARNING:superset.utils.cache_manager:Falling back to the built-in cache, that stores data in the metadata database, for the following cache: `EXPLORE_FORM_DATA_CACHE_CONFIG`. It is recommended to use `RedisCache`, `MemcachedCache` or another dedicated caching backend for production deployments
superset_app | Skipping local overrides
superset_app | Starting web app...
superset_app | usage: gunicorn [OPTIONS] [APP_MODULE]
superset_app | gunicorn: error: argument --max-requests: expected one argument
superset_app exited with code 2
superset_worker_beat | ERROR: Pidfile (/tmp/celerybeat.pid) already exists.
superset_worker_beat | Seems we're already running? (pid: 8)
superset_worker_beat | Loaded your LOCAL configuration at [/app/docker/pythonpath_dev/superset_config.py]
superset_worker_beat | celery beat v5.2.2 (dawn-chorus) is starting.
superset_worker | Loaded your LOCAL configuration at [/app/docker/pythonpath_dev/superset_config.py]
superset_worker |
superset_worker | -------------- celery@c4a746c651f6 v5.2.2 (dawn-chorus)
superset_worker | --- ***** -----
superset_worker | -- ******* ---- Linux-5.10.104-linuxkit-x86_64-with-glibc2.2.5 2022-07-18 14:34:16
superset_worker | - *** --- * ---
superset_worker | - ** ---------- [config]
superset_worker | - ** ---------- .> app: __main__:0x4025c7e430
superset_worker | - ** ---------- .> transport: redis://redis:6379/0
superset_worker | - ** ---------- .> results: redis://redis:6379/1
superset_worker | - *** --- * --- .> concurrency: 4 (prefork)
superset_worker | -- ******* ---- .> task events: OFF (enable -E to monitor tasks in this worker)
superset_worker | --- ***** -----
superset_worker | -------------- [queues]
superset_worker | .> celery exchange=celery(direct) key=celery
superset_worker |
superset_worker |
superset_worker | [tasks]
superset_worker | . cache-warmup
superset_worker | . cache_chart_thumbnail
superset_worker | . cache_dashboard_thumbnail
superset_worker | . load_chart_data_into_cache
superset_worker | . load_explore_json_into_cache
superset_worker | . reports.execute
superset_worker | . reports.prune_log
superset_worker | . reports.scheduler
superset_worker | . sql_lab.get_sql_results
superset_worker |
superset_worker | /usr/local/lib/python3.8/site-packages/celery/platforms.py:840: SecurityWarning: You're running the worker with superuser privileges: this is
superset_worker | absolutely not recommended!
superset_worker |
superset_worker | Please specify a different user using the --uid option.
superset_worker |
superset_worker | User information: uid=0 euid=0 gid=0 egid=0
superset_worker |
superset_worker | warnings.warn(SecurityWarning(ROOT_DISCOURAGED.format(
superset_worker | [2022-07-18 14:34:16,396: WARNING/MainProcess] /usr/local/lib/python3.8/site-packages/celery/app/utils.py:204: CDeprecationWarning:
superset_worker | The 'CELERY_IMPORTS' setting is deprecated and scheduled for removal in
superset_worker | version 6.0.0. Use the imports instead
superset_worker |
superset_worker | deprecated.warn(description=f'The {setting!r} setting',
superset_worker |
superset_worker | [2022-07-18 14:34:16,398: WARNING/MainProcess] /usr/local/lib/python3.8/site-packages/celery/app/utils.py:204: CDeprecationWarning:
superset_worker | The 'BROKER_URL' setting is deprecated and scheduled for removal in
superset_worker | version 6.0.0. Use the broker_url instead
superset_worker |
superset_worker | deprecated.warn(description=f'The {setting!r} setting',
superset_worker |
superset_worker | [2022-07-18 14:34:16,398: WARNING/MainProcess] /usr/local/lib/python3.8/site-packages/celery/app/utils.py:204: CDeprecationWarning:
superset_worker | The 'CELERYBEAT_SCHEDULE' setting is deprecated and scheduled for removal in
superset_worker | version 6.0.0. Use the beat_schedule instead
superset_worker |
superset_worker | deprecated.warn(description=f'The {setting!r} setting',
superset_worker |
superset_worker | [2022-07-18 14:34:16,399: WARNING/MainProcess] /usr/local/lib/python3.8/site-packages/celery/app/utils.py:204: CDeprecationWarning:
superset_worker | The 'CELERY_RESULT_BACKEND' setting is deprecated and scheduled for removal in
superset_worker | version 6.0.0. Use the result_backend instead
superset_worker |
superset_worker | deprecated.warn(description=f'The {setting!r} setting',
superset_worker |
superset_worker | [2022-07-18 14:34:16,399: WARNING/MainProcess] /usr/local/lib/python3.8/site-packages/celery/app/utils.py:204: CDeprecationWarning:
superset_worker | The 'CELERY_ACKS_LATE' setting is deprecated and scheduled for removal in
superset_worker | version 6.0.0. Use the task_acks_late instead
superset_worker |
superset_worker | deprecated.warn(description=f'The {setting!r} setting',
superset_worker |
superset_worker | [2022-07-18 14:34:16,400: WARNING/MainProcess] /usr/local/lib/python3.8/site-packages/celery/app/utils.py:204: CDeprecationWarning:
superset_worker | The 'CELERYD_PREFETCH_MULTIPLIER' setting is deprecated and scheduled for removal in
superset_worker | version 6.0.0. Use the worker_prefetch_multiplier instead
superset_worker |
superset_worker | deprecated.warn(description=f'The {setting!r} setting',
superset_worker |
superset_worker | [2022-07-18 14:34:16,400: WARNING/MainProcess] Please run `celery upgrade settings path/to/settings.py` to avoid these warnings and to allow a smoother upgrade to Celery 6.0.
superset_worker_beat | Skipping local overrides
superset_worker_beat | Starting Celery beat...
superset_worker | [2022-07-18 14:34:17,489: INFO/MainProcess] Connected to redis://redis:6379/0
superset_worker | [2022-07-18 14:34:17,499: INFO/MainProcess] mingle: searching for neighbors
superset_worker | [2022-07-18 14:34:18,545: INFO/MainProcess] mingle: all alone
superset_worker | [2022-07-18 14:34:18,624: INFO/MainProcess] celery@c4a746c651f6 ready.
superset_init | INFO [alembic.runtime.migration] Context impl PostgresqlImpl.
superset_init | INFO [alembic.runtime.migration] Will assume transactional DDL.
superset_app | Skipping local overrides
superset_app | Starting web app...
superset_init | Loaded your LOCAL configuration at [/app/docker/pythonpath_dev/superset_config.py]
superset_init |
superset_init | ######################################################################
superset_init |
superset_init |
superset_init | Init Step 1/4 [Complete] -- Applying DB migrations
superset_init |
superset_init |
superset_init | ######################################################################
superset_init |
superset_init |
superset_init | ######################################################################
superset_init |
superset_init |
superset_init | Init Step 2/4 [Starting] -- Setting up admin user ( admin / admin )
superset_init |
superset_init |
superset_init | ######################################################################
superset_init |
superset_app | usage: gunicorn [OPTIONS] [APP_MODULE]
superset_app | gunicorn: error: argument --max-requests: expected one argument
superset_app exited with code 2
superset_worker_beat | --------------------------------------------------------------------------------
superset_worker_beat | WARNING
superset_worker_beat | --------------------------------------------------------------------------------
superset_worker_beat | A Default SECRET_KEY was detected, please use superset_config.py to override it.
superset_worker_beat | Use a strong complex alphanumeric string and use a tool to help you generate
superset_worker_beat | a sufficiently random sequence, ex: openssl rand -base64 42
superset_worker_beat | --------------------------------------------------------------------------------
superset_worker_beat | --------------------------------------------------------------------------------
superset_worker_beat | logging was configured successfully
superset_worker_beat | 2022-07-18 14:34:26,721:INFO:superset.utils.logging_configurator:logging was configured successfully
superset_worker_beat | 2022-07-18 14:34:26,732:INFO:root:Configured event logger of type <class 'superset.utils.log.DBEventLogger'>
superset_worker_beat | Falling back to the built-in cache, that stores data in the metadata database, for the following cache: `FILTER_STATE_CACHE_CONFIG`. It is recommended to use `RedisCache`, `MemcachedCache` or another dedicated caching backend for production deployments
superset_worker_beat | 2022-07-18 14:34:26,747:WARNING:superset.utils.cache_manager:Falling back to the built-in cache, that stores data in the metadata database, for the following cache: `FILTER_STATE_CACHE_CONFIG`. It is recommended to use `RedisCache`, `MemcachedCache` or another dedicated caching backend for production deployments
superset_worker_beat | Falling back to the built-in cache, that stores data in the metadata database, for the following cache: `EXPLORE_FORM_DATA_CACHE_CONFIG`. It is recommended to use `RedisCache`, `MemcachedCache` or another dedicated caching backend for production deployments
superset_worker_beat | 2022-07-18 14:34:26,764:WARNING:superset.utils.cache_manager:Falling back to the built-in cache, that stores data in the metadata database, for the following cache: `EXPLORE_FORM_DATA_CACHE_CONFIG`. It is recommended to use `RedisCache`, `MemcachedCache` or another dedicated caching backend for production deployments
superset_worker_beat | Loaded your LOCAL configuration at [/app/docker/pythonpath_dev/superset_config.py]
superset_worker_beat | celery beat v5.2.2 (dawn-chorus) is starting.
superset_worker_beat | ERROR: Pidfile (/tmp/celerybeat.pid) already exists.
superset_worker_beat | Seems we're already running? (pid: 8)
superset_init | --------------------------------------------------------------------------------
superset_init | WARNING
superset_init | --------------------------------------------------------------------------------
superset_init | A Default SECRET_KEY was detected, please use superset_config.py to override it.
superset_init | Use a strong complex alphanumeric string and use a tool to help you generate
superset_init | a sufficiently random sequence, ex: openssl rand -base64 42
superset_init | --------------------------------------------------------------------------------
superset_init | --------------------------------------------------------------------------------
superset_init | logging was configured successfully
superset_init | 2022-07-18 14:34:35,164:INFO:superset.utils.logging_configurator:logging was configured successfully
superset_init | 2022-07-18 14:34:35,194:INFO:root:Configured event logger of type <class 'superset.utils.log.DBEventLogger'>
superset_init | Falling back to the built-in cache, that stores data in the metadata database, for the following cache: `FILTER_STATE_CACHE_CONFIG`. It is recommended to use `RedisCache`, `MemcachedCache` or another dedicated caching backend for production deployments
superset_init | 2022-07-18 14:34:35,208:WARNING:superset.utils.cache_manager:Falling back to the built-in cache, that stores data in the metadata database, for the following cache: `FILTER_STATE_CACHE_CONFIG`. It is recommended to use `RedisCache`, `MemcachedCache` or another dedicated caching backend for production deployments
superset_init | Falling back to the built-in cache, that stores data in the metadata database, for the following cache: `EXPLORE_FORM_DATA_CACHE_CONFIG`. It is recommended to use `RedisCache`, `MemcachedCache` or another dedicated caching backend for production deployments
superset_init | 2022-07-18 14:34:35,223:WARNING:superset.utils.cache_manager:Falling back to the built-in cache, that stores data in the metadata database, for the following cache: `EXPLORE_FORM_DATA_CACHE_CONFIG`. It is recommended to use `RedisCache`, `MemcachedCache` or another dedicated caching backend for production deployments
superset_worker_beat exited with code 73
superset_worker_beat | Skipping local overrides
superset_worker_beat | Starting Celery beat...
superset_app | Skipping local overrides
superset_app | Starting web app...
superset_app | usage: gunicorn [OPTIONS] [APP_MODULE]
superset_app | gunicorn: error: argument --max-requests: expected one argument
superset_app exited with code 2
superset_init | Loaded your LOCAL configuration at [/app/docker/pythonpath_dev/superset_config.py]
superset_init | Recognized Database Authentications.
superset_init | Error! User already exists admin
superset_init |
superset_init | ######################################################################
superset_init |
superset_init |
superset_init | Init Step 2/4 [Complete] -- Setting up admin user
superset_init |
superset_init |
superset_init | ######################################################################
superset_init |
superset_init |
superset_init | ######################################################################
superset_init |
superset_init |
superset_init | Init Step 3/4 [Starting] -- Setting up roles and perms
superset_init |
superset_init |
superset_init | ######################################################################
superset_init |
superset_worker_beat | --------------------------------------------------------------------------------
superset_worker_beat | WARNING
superset_worker_beat | --------------------------------------------------------------------------------
superset_worker_beat | A Default SECRET_KEY was detected, please use superset_config.py to override it.
superset_worker_beat | Use a strong complex alphanumeric string and use a tool to help you generate
superset_worker_beat | a sufficiently random sequence, ex: openssl rand -base64 42
superset_worker_beat | --------------------------------------------------------------------------------
superset_worker_beat | --------------------------------------------------------------------------------
superset_worker_beat | logging was configured successfully
superset_worker_beat | 2022-07-18 14:34:45,750:INFO:superset.utils.logging_configurator:logging was configured successfully
superset_worker_beat | 2022-07-18 14:34:45,761:INFO:root:Configured event logger of type <class 'superset.utils.log.DBEventLogger'>
superset_worker_beat | Falling back to the built-in cache, that stores data in the metadata database, for the following cache: `FILTER_STATE_CACHE_CONFIG`. It is recommended to use `RedisCache`, `MemcachedCache` or another dedicated caching backend for production deployments
superset_worker_beat | 2022-07-18 14:34:45,773:WARNING:superset.utils.cache_manager:Falling back to the built-in cache, that stores data in the metadata database, for the following cache: `FILTER_STATE_CACHE_CONFIG`. It is recommended to use `RedisCache`, `MemcachedCache` or another dedicated caching backend for production deployments
superset_worker_beat | Falling back to the built-in cache, that stores data in the metadata database, for the following cache: `EXPLORE_FORM_DATA_CACHE_CONFIG`. It is recommended to use `RedisCache`, `MemcachedCache` or another dedicated caching backend for production deployments
superset_worker_beat | 2022-07-18 14:34:45,796:WARNING:superset.utils.cache_manager:Falling back to the built-in cache, that stores data in the metadata database, for the following cache: `EXPLORE_FORM_DATA_CACHE_CONFIG`. It is recommended to use `RedisCache`, `MemcachedCache` or another dedicated caching backend for production deployments
superset_worker_beat | Loaded your LOCAL configuration at [/app/docker/pythonpath_dev/superset_config.py]
superset_worker_beat | celery beat v5.2.2 (dawn-chorus) is starting.
superset_worker_beat | ERROR: Pidfile (/tmp/celerybeat.pid) already exists.
superset_worker_beat | Seems we're already running? (pid: 8)
superset_worker_beat exited with code 73
superset_worker_beat | Skipping local overrides
superset_worker_beat | Starting Celery beat...
superset_init | --------------------------------------------------------------------------------
superset_init | WARNING
superset_init | --------------------------------------------------------------------------------
superset_init | A Default SECRET_KEY was detected, please use superset_config.py to override it.
superset_init | Use a strong complex alphanumeric string and use a tool to help you generate
superset_init | a sufficiently random sequence, ex: openssl rand -base64 42
superset_init | --------------------------------------------------------------------------------
superset_init | --------------------------------------------------------------------------------
superset_init | logging was configured successfully
superset_init | 2022-07-18 14:34:56,616:INFO:superset.utils.logging_configurator:logging was configured successfully
superset_init | 2022-07-18 14:34:56,639:INFO:root:Configured event logger of type <class 'superset.utils.log.DBEventLogger'>
superset_init | Falling back to the built-in cache, that stores data in the metadata database, for the following cache: `FILTER_STATE_CACHE_CONFIG`. It is recommended to use `RedisCache`, `MemcachedCache` or another dedicated caching backend for production deployments
superset_init | 2022-07-18 14:34:56,652:WARNING:superset.utils.cache_manager:Falling back to the built-in cache, that stores data in the metadata database, for the following cache: `FILTER_STATE_CACHE_CONFIG`. It is recommended to use `RedisCache`, `MemcachedCache` or another dedicated caching backend for production deployments
superset_init | Falling back to the built-in cache, that stores data in the metadata database, for the following cache: `EXPLORE_FORM_DATA_CACHE_CONFIG`. It is recommended to use `RedisCache`, `MemcachedCache` or another dedicated caching backend for production deployments
superset_init | 2022-07-18 14:34:56,666:WARNING:superset.utils.cache_manager:Falling back to the built-in cache, that stores data in the metadata database, for the following cache: `EXPLORE_FORM_DATA_CACHE_CONFIG`. It is recommended to use `RedisCache`, `MemcachedCache` or another dedicated caching backend for production deployments
superset_worker_beat | --------------------------------------------------------------------------------
superset_worker_beat | WARNING
superset_worker_beat | --------------------------------------------------------------------------------
superset_worker_beat | A Default SECRET_KEY was detected, please use superset_config.py to override it.
superset_worker_beat | Use a strong complex alphanumeric string and use a tool to help you generate
superset_worker_beat | a sufficiently random sequence, ex: openssl rand -base64 42
superset_worker_beat | --------------------------------------------------------------------------------
superset_worker_beat | --------------------------------------------------------------------------------
superset_worker_beat | logging was configured successfully
superset_worker_beat | 2022-07-18 14:35:03,295:INFO:superset.utils.logging_configurator:logging was configured successfully
superset_worker_beat | 2022-07-18 14:35:03,305:INFO:root:Configured event logger of type <class 'superset.utils.log.DBEventLogger'>
superset_worker_beat | Falling back to the built-in cache, that stores data in the metadata database, for the following cache: `FILTER_STATE_CACHE_CONFIG`. It is recommended to use `RedisCache`, `MemcachedCache` or another dedicated caching backend for production deployments
superset_worker_beat | 2022-07-18 14:35:03,319:WARNING:superset.utils.cache_manager:Falling back to the built-in cache, that stores data in the metadata database, for the following cache: `FILTER_STATE_CACHE_CONFIG`. It is recommended to use `RedisCache`, `MemcachedCache` or another dedicated caching backend for production deployments
superset_worker_beat | Falling back to the built-in cache, that stores data in the metadata database, for the following cache: `EXPLORE_FORM_DATA_CACHE_CONFIG`. It is recommended to use `RedisCache`, `MemcachedCache` or another dedicated caching backend for production deployments
superset_worker_beat | 2022-07-18 14:35:03,336:WARNING:superset.utils.cache_manager:Falling back to the built-in cache, that stores data in the metadata database, for the following cache: `EXPLORE_FORM_DATA_CACHE_CONFIG`. It is recommended to use `RedisCache`, `MemcachedCache` or another dedicated caching backend for production deployments
superset_app | Skipping local overrides
superset_app | Starting web app...
superset_app | usage: gunicorn [OPTIONS] [APP_MODULE]
superset_app | gunicorn: error: argument --max-requests: expected one argument
superset_app exited with code 2
superset_init | Syncing role definition
superset_init | 2022-07-18 14:35:08,982:INFO:superset.security.manager:Syncing role definition
superset_init | Syncing Admin perms
superset_init | 2022-07-18 14:35:09,030:INFO:superset.security.manager:Syncing Admin perms
superset_init | Syncing Alpha perms
superset_init | 2022-07-18 14:35:09,354:INFO:superset.security.manager:Syncing Alpha perms
superset_init | Syncing Gamma perms
superset_init | 2022-07-18 14:35:09,694:INFO:superset.security.manager:Syncing Gamma perms
superset_init | Syncing granter perms
superset_init | 2022-07-18 14:35:10,023:INFO:superset.security.manager:Syncing granter perms
superset_init | Syncing sql_lab perms
superset_init | 2022-07-18 14:35:10,336:INFO:superset.security.manager:Syncing sql_lab perms
superset_init | Fetching a set of all perms to lookup which ones are missing
superset_init | 2022-07-18 14:35:10,647:INFO:superset.security.manager:Fetching a set of all perms to lookup which ones are missing
superset_init | Creating missing datasource permissions.
superset_init | 2022-07-18 14:35:10,939:INFO:superset.security.manager:Creating missing datasource permissions.
superset_init | Creating missing database permissions.
superset_init | 2022-07-18 14:35:10,958:INFO:superset.security.manager:Creating missing database permissions.
superset_init | Cleaning faulty perms
superset_init | 2022-07-18 14:35:10,984:INFO:superset.security.manager:Cleaning faulty perms
superset_init | Loaded your LOCAL configuration at [/app/docker/pythonpath_dev/superset_config.py]
superset_worker_beat | Loaded your LOCAL configuration at [/app/docker/pythonpath_dev/superset_config.py]
superset_worker_beat | celery beat v5.2.2 (dawn-chorus) is starting.
superset_worker_beat | ERROR: Pidfile (/tmp/celerybeat.pid) already exists.
superset_worker_beat | Seems we're already running? (pid: 8)
superset_init |
superset_init | ######################################################################
superset_init |
superset_init |
superset_init | Init Step 3/4 [Complete] -- Setting up roles and perms
superset_init |
superset_init |
superset_init | ######################################################################
superset_init |
superset_init |
superset_init | ######################################################################
superset_init |
superset_init |
superset_init | Init Step 4/4 [Starting] -- Loading examples
superset_init |
superset_init |
superset_init | ######################################################################
superset_init |
superset_worker_beat exited with code 73
superset_worker_beat | Skipping local overrides
superset_worker_beat | Starting Celery beat...
superset_worker_beat | --------------------------------------------------------------------------------
superset_worker_beat | WARNING
superset_worker_beat | --------------------------------------------------------------------------------
superset_worker_beat | A Default SECRET_KEY was detected, please use superset_config.py to override it.
superset_worker_beat | Use a strong complex alphanumeric string and use a tool to help you generate
superset_worker_beat | a sufficiently random sequence, ex: openssl rand -base64 42
superset_worker_beat | --------------------------------------------------------------------------------
superset_worker_beat | --------------------------------------------------------------------------------
superset_worker_beat | logging was configured successfully
superset_worker_beat | 2022-07-18 14:35:21,535:INFO:superset.utils.logging_configurator:logging was configured successfully
superset_worker_beat | 2022-07-18 14:35:21,548:INFO:root:Configured event logger of type <class 'superset.utils.log.DBEventLogger'>
superset_worker_beat | Falling back to the built-in cache, that stores data in the metadata database, for the following cache: `FILTER_STATE_CACHE_CONFIG`. It is recommended to use `RedisCache`, `MemcachedCache` or another dedicated caching backend for production deployments
superset_worker_beat | 2022-07-18 14:35:21,562:WARNING:superset.utils.cache_manager:Falling back to the built-in cache, that stores data in the metadata database, for the following cache: `FILTER_STATE_CACHE_CONFIG`. It is recommended to use `RedisCache`, `MemcachedCache` or another dedicated caching backend for production deployments
superset_worker_beat | Falling back to the built-in cache, that stores data in the metadata database, for the following cache: `EXPLORE_FORM_DATA_CACHE_CONFIG`. It is recommended to use `RedisCache`, `MemcachedCache` or another dedicated caching backend for production deployments
superset_worker_beat | 2022-07-18 14:35:21,590:WARNING:superset.utils.cache_manager:Falling back to the built-in cache, that stores data in the metadata database, for the following cache: `EXPLORE_FORM_DATA_CACHE_CONFIG`. It is recommended to use `RedisCache`, `MemcachedCache` or another dedicated caching backend for production deployments
superset_init | --------------------------------------------------------------------------------
superset_init | WARNING
superset_init | --------------------------------------------------------------------------------
superset_init | A Default SECRET_KEY was detected, please use superset_config.py to override it.
superset_init | Use a strong complex alphanumeric string and use a tool to help you generate
superset_init | a sufficiently random sequence, ex: openssl rand -base64 42
superset_init | --------------------------------------------------------------------------------
superset_init | --------------------------------------------------------------------------------
superset_init | logging was configured successfully
superset_init | 2022-07-18 14:35:24,127:INFO:superset.utils.logging_configurator:logging was configured successfully
superset_init | 2022-07-18 14:35:24,153:INFO:root:Configured event logger of type <class 'superset.utils.log.DBEventLogger'>
superset_init | Falling back to the built-in cache, that stores data in the metadata database, for the following cache: `FILTER_STATE_CACHE_CONFIG`. It is recommended to use `RedisCache`, `MemcachedCache` or another dedicated caching backend for production deployments
superset_init | 2022-07-18 14:35:24,170:WARNING:superset.utils.cache_manager:Falling back to the built-in cache, that stores data in the metadata database, for the following cache: `FILTER_STATE_CACHE_CONFIG`. It is recommended to use `RedisCache`, `MemcachedCache` or another dedicated caching backend for production deployments
superset_init | Falling back to the built-in cache, that stores data in the metadata database, for the following cache: `EXPLORE_FORM_DATA_CACHE_CONFIG`. It is recommended to use `RedisCache`, `MemcachedCache` or another dedicated caching backend for production deployments
superset_init | 2022-07-18 14:35:24,186:WARNING:superset.utils.cache_manager:Falling back to the built-in cache, that stores data in the metadata database, for the following cache: `EXPLORE_FORM_DATA_CACHE_CONFIG`. It is recommended to use `RedisCache`, `MemcachedCache` or another dedicated caching backend for production deployments
superset_worker_beat | Stale pidfile exists - Removing it.
superset_worker_beat | [2022-07-18 14:35:29,976: INFO/MainProcess] beat: Starting...
superset_worker_beat | [2022-07-18 14:35:30,040: INFO/MainProcess] Scheduler: Sending due task reports.scheduler (reports.scheduler)
superset_worker | [2022-07-18 14:35:30,089: INFO/MainProcess] Task reports.scheduler[b9ac068c-a9b5-4b32-a9ba-24ac0f3fb7f2] received
superset_worker | [2022-07-18 14:35:30,227: INFO/ForkPoolWorker-1] Task reports.scheduler[b9ac068c-a9b5-4b32-a9ba-24ac0f3fb7f2] succeeded in 0.11053812500904314s: None
superset_init | Loaded your LOCAL configuration at [/app/docker/pythonpath_dev/superset_config.py]
superset_init | Loading examples metadata and related data into examples
superset_init | Creating default CSS templates
superset_init | Loading [World Bank's Health Nutrition and Population Stats]
superset_init | Traceback (most recent call last):
superset_init | File "/usr/local/lib/python3.8/urllib/request.py", line 1354, in do_open
superset_init | h.request(req.get_method(), req.selector, req.data, headers,
superset_init | File "/usr/local/lib/python3.8/http/client.py", line 1256, in request
superset_init | self._send_request(method, url, body, headers, encode_chunked)
superset_init | File "/usr/local/lib/python3.8/http/client.py", line 1302, in _send_request
superset_init | self.endheaders(body, encode_chunked=encode_chunked)
superset_init | File "/usr/local/lib/python3.8/http/client.py", line 1251, in endheaders
superset_init | self._send_output(message_body, encode_chunked=encode_chunked)
superset_init | File "/usr/local/lib/python3.8/http/client.py", line 1011, in _send_output
superset_init | self.send(msg)
superset_init | File "/usr/local/lib/python3.8/http/client.py", line 951, in send
superset_init | self.connect()
superset_init | File "/usr/local/lib/python3.8/http/client.py", line 1418, in connect
superset_init | super().connect()
superset_init | File "/usr/local/lib/python3.8/http/client.py", line 922, in connect
superset_init | self.sock = self._create_connection(
superset_init | File "/usr/local/lib/python3.8/socket.py", line 808, in create_connection
superset_init | raise err
superset_init | File "/usr/local/lib/python3.8/socket.py", line 796, in create_connection
superset_init | sock.connect(sa)
superset_init | OSError: [Errno 99] Cannot assign requested address
superset_init |
superset_init | During handling of the above exception, another exception occurred:
superset_init |
superset_init | Traceback (most recent call last):
superset_init | File "/usr/local/bin/superset", line 33, in <module>
superset_init | sys.exit(load_entry_point('apache-superset', 'console_scripts', 'superset')())
superset_init | File "/usr/local/lib/python3.8/site-packages/click/core.py", line 1128, in __call__
superset_init | return self.main(*args, **kwargs)
superset_init | File "/usr/local/lib/python3.8/site-packages/flask/cli.py", line 601, in main
superset_init | return super().main(*args, **kwargs)
superset_init | File "/usr/local/lib/python3.8/site-packages/click/core.py", line 1053, in main
superset_init | rv = self.invoke(ctx)
superset_init | File "/usr/local/lib/python3.8/site-packages/click/core.py", line 1659, in invoke
superset_init | return _process_result(sub_ctx.command.invoke(sub_ctx))
superset_init | File "/usr/local/lib/python3.8/site-packages/click/core.py", line 1395, in invoke
superset_init | return ctx.invoke(self.callback, **ctx.params)
superset_init | File "/usr/local/lib/python3.8/site-packages/click/core.py", line 754, in invoke
superset_init | return __callback(*args, **kwargs)
superset_init | File "/usr/local/lib/python3.8/site-packages/click/decorators.py", line 26, in new_func
superset_init | return f(get_current_context(), *args, **kwargs)
superset_init | File "/usr/local/lib/python3.8/site-packages/flask/cli.py", line 445, in decorator
superset_init | return __ctx.invoke(f, *args, **kwargs)
superset_init | File "/usr/local/lib/python3.8/site-packages/click/core.py", line 754, in invoke
superset_init | return __callback(*args, **kwargs)
superset_init | File "/app/superset/cli/examples.py", line 113, in load_examples
superset_init | load_examples_run(load_test_data, load_big_data, only_metadata, force)
superset_init | File "/app/superset/cli/examples.py", line 49, in load_examples_run
superset_init | examples.load_world_bank_health_n_pop(only_metadata, force)
superset_init | File "/app/superset/examples/world_bank.py", line 59, in load_world_bank_health_n_pop
superset_init | data = get_example_data("countries.json.gz")
superset_init | File "/app/superset/examples/helpers.py", line 79, in get_example_data
superset_init | content = request.urlopen( # pylint: disable=consider-using-with
superset_init | File "/usr/local/lib/python3.8/urllib/request.py", line 222, in urlopen
superset_init | return opener.open(url, data, timeout)
superset_init | File "/usr/local/lib/python3.8/urllib/request.py", line 531, in open
superset_init | response = meth(req, response)
superset_init | File "/usr/local/lib/python3.8/urllib/request.py", line 640, in http_response
superset_init | response = self.parent.error(
superset_init | File "/usr/local/lib/python3.8/urllib/request.py", line 563, in error
superset_init | result = self._call_chain(*args)
superset_init | File "/usr/local/lib/python3.8/urllib/request.py", line 502, in _call_chain
superset_init | result = func(*args)
superset_init | File "/usr/local/lib/python3.8/urllib/request.py", line 755, in http_error_302
superset_init | return self.parent.open(new, timeout=req.timeout)
superset_init | File "/usr/local/lib/python3.8/urllib/request.py", line 531, in open
superset_init | response = meth(req, response)
superset_init | File "/usr/local/lib/python3.8/urllib/request.py", line 640, in http_response
superset_init | response = self.parent.error(
superset_init | File "/usr/local/lib/python3.8/urllib/request.py", line 563, in error
superset_init | result = self._call_chain(*args)
superset_init | File "/usr/local/lib/python3.8/urllib/request.py", line 502, in _call_chain
superset_init | result = func(*args)
superset_init | File "/usr/local/lib/python3.8/urllib/request.py", line 755, in http_error_302
superset_init | return self.parent.open(new, timeout=req.timeout)
superset_init | File "/usr/local/lib/python3.8/urllib/request.py", line 525, in open
superset_init | response = self._open(req, data)
superset_init | File "/usr/local/lib/python3.8/urllib/request.py", line 542, in _open
superset_init | result = self._call_chain(self.handle_open, protocol, protocol +
superset_init | File "/usr/local/lib/python3.8/urllib/request.py", line 502, in _call_chain
superset_init | result = func(*args)
superset_init | File "/usr/local/lib/python3.8/urllib/request.py", line 1397, in https_open
superset_init | return self.do_open(http.client.HTTPSConnection, req,
superset_init | File "/usr/local/lib/python3.8/urllib/request.py", line 1357, in do_open
superset_init | raise URLError(err)
superset_init | urllib.error.URLError: <urlopen error [Errno 99] Cannot assign requested address>
superset_init exited with code 1
superset_app | Skipping local overrides
superset_app | Starting web app...
superset_app | usage: gunicorn [OPTIONS] [APP_MODULE]
superset_app | gunicorn: error: argument --max-requests: expected one argument
superset_app exited with code 2
superset_worker_beat | [2022-07-18 14:36:00,030: INFO/MainProcess] Scheduler: Sending due task reports.scheduler (reports.scheduler)
superset_worker | [2022-07-18 14:36:00,064: INFO/MainProcess] Task reports.scheduler[c89c6a44-c584-4e0b-9a79-e0a719149022] received
superset_worker | [2022-07-18 14:36:00,115: INFO/ForkPoolWorker-1] Task reports.scheduler[c89c6a44-c584-4e0b-9a79-e0a719149022] succeeded in 0.04363124999508727s: None
superset_app | Skipping local overrides
superset_app | Starting web app...
superset_app | usage: gunicorn [OPTIONS] [APP_MODULE]
superset_app | gunicorn: error: argument --max-requests: expected one argument
superset_worker_beat | [2022-07-18 14:37:00,036: INFO/MainProcess] Scheduler: Sending due task reports.scheduler (reports.scheduler)
superset_worker | [2022-07-18 14:37:00,063: INFO/MainProcess] Task reports.scheduler[f2044f9e-a42c-4d65-8648-7a7bad478008] received
superset_worker | [2022-07-18 14:37:00,152: INFO/ForkPoolWorker-1] Task reports.scheduler[f2044f9e-a42c-4d65-8648-7a7bad478008] succeeded in 0.0697625830071047s: None
superset_app exited with code 2
superset_worker_beat | [2022-07-18 14:38:00,047: INFO/MainProcess] Scheduler: Sending due task reports.scheduler (reports.scheduler)
superset_worker | [2022-07-18 14:38:00,082: INFO/MainProcess] Task reports.scheduler[29b8df55-2994-456a-b433-5b02f6f8fd6c] received
superset_worker | [2022-07-18 14:38:00,218: INFO/ForkPoolWorker-1] Task reports.scheduler[29b8df55-2994-456a-b433-5b02f6f8fd6c] succeeded in 0.11490391600818839s: None
superset_app | Skipping local overrides
superset_app | Starting web app...
superset_app | usage: gunicorn [OPTIONS] [APP_MODULE]
superset_app | gunicorn: error: argument --max-requests: expected one argument
superset_app exited with code 2
superset_worker_beat | [2022-07-18 14:39:00,030: INFO/MainProcess] Scheduler: Sending due task reports.scheduler (reports.scheduler)
superset_worker | [2022-07-18 14:39:00,067: INFO/MainProcess] Task reports.scheduler[91911a3a-54b9-4bb3-b886-02b6a5f18f4c] received
superset_worker | [2022-07-18 14:39:00,151: INFO/ForkPoolWorker-1] Task reports.scheduler[91911a3a-54b9-4bb3-b886-02b6a5f18f4c] succeeded in 0.06387108299531974s: None
superset_app | Skipping local overrides
superset_app | Starting web app...
superset_app | usage: gunicorn [OPTIONS] [APP_MODULE]
superset_app | gunicorn: error: argument --max-requests: expected one argument
superset_app exited with code 2
```
--
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-unsubscribe@superset.apache.org.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For additional commands, e-mail: notifications-help@superset.apache.org
[GitHub] [superset] Chrisfufu commented on issue #20744: docker-compose up failed
Posted by GitBox <gi...@apache.org>.
Chrisfufu commented on issue #20744:
URL: https://github.com/apache/superset/issues/20744#issuecomment-1187602504
I am facing the same issue!
--
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-unsubscribe@superset.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For additional commands, e-mail: notifications-help@superset.apache.org
[GitHub] [superset] srinify closed issue #20744: docker-compose up failed
Posted by GitBox <gi...@apache.org>.
srinify closed issue #20744: docker-compose up failed
URL: https://github.com/apache/superset/issues/20744
--
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-unsubscribe@superset.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For additional commands, e-mail: notifications-help@superset.apache.org
[GitHub] [superset] srinify commented on issue #20744: docker-compose up failed
Posted by GitBox <gi...@apache.org>.
srinify commented on issue #20744:
URL: https://github.com/apache/superset/issues/20744#issuecomment-1189548485
Closing for now!
--
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-unsubscribe@superset.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For additional commands, e-mail: notifications-help@superset.apache.org
[GitHub] [superset] mlategan commented on issue #20744: docker-compose up failed
Posted by GitBox <gi...@apache.org>.
mlategan commented on issue #20744:
URL: https://github.com/apache/superset/issues/20744#issuecomment-1187611023
Same here. gunicorn: error: argument --max-requests: expected one argument repeatedly.
--
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-unsubscribe@superset.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For additional commands, e-mail: notifications-help@superset.apache.org
[GitHub] [superset] Chrisfufu commented on issue #20744: docker-compose up failed
Posted by GitBox <gi...@apache.org>.
Chrisfufu commented on issue #20744:
URL: https://github.com/apache/superset/issues/20744#issuecomment-1187690512
solved by pulling latest updates from master branch
--
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-unsubscribe@superset.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For additional commands, e-mail: notifications-help@superset.apache.org