fleimgruber opened a new issue, #27288:
URL: https://github.com/apache/superset/issues/27288

   ### Bug description
   
   superset_init container fails to create example data sets
   
   ### How to reproduce the bug
   
   Following 
https://superset.apache.org/docs/installation/installing-superset-using-docker-compose
   
   1. git clone https://github.com/apache/superset.git
   2. cd superset
   3. podman compose -f docker-compose-non-dev.yml up
   
   ### Screenshots/recordings
   
   _No response_
   
   ### Superset version
   
   master / latest-dev
   
   ### Python version
   
   3.9
   
   ### Node version
   
   16
   
   ### Browser
   
   Chrome
   
   ### Additional context
   
   `podman logs superset_init`:
   
   ```
   Skipping local overrides
   Unknown Operation!!!
   
   ######################################################################
   
   
   Init Step 1/4 [Starting] -- Applying DB migrations
   
   
   ######################################################################
   
   logging was configured successfully
   2024-02-28 14:29:07,310:INFO:superset.utils.logging_configurator:logging was 
configured successfully
   2024-02-28 14:29:07,315:INFO:root:Configured event logger of type <class 
'superset.utils.log.DBEventLogger'>
   /usr/local/lib/python3.9/site-packages/flask_limiter/extension.py:293: 
UserWarning: Using the in-memory storage for tracking rate limits as no storage 
was explicitly specified. This is not recommended for production use. See: 
https://flask-limiter.readthedocs.io#configuring-a-storage-backend for 
documentation about configuring the storage backend.
     warnings.warn(
   INFO  [alembic.runtime.migration] Context impl PostgresqlImpl.
   INFO  [alembic.runtime.migration] Will assume transactional DDL.
   Loaded your LOCAL configuration at 
[/app/docker/pythonpath_dev/superset_config.py]
   ERROR [flask_migrate] Error: Can't locate revision identified by 
'17fcea065655'
   Skipping local overrides
   Unknown Operation!!!
   
   ######################################################################
   
   
   Init Step 1/4 [Starting] -- Applying DB migrations
   
   
   ######################################################################
   
   logging was configured successfully
   2024-02-28 14:31:34,359:INFO:superset.utils.logging_configurator:logging was 
configured successfully
   2024-02-28 14:31:34,363:INFO:root:Configured event logger of type <class 
'superset.utils.log.DBEventLogger'>
   /usr/local/lib/python3.9/site-packages/flask_limiter/extension.py:293: 
UserWarning: Using the in-memory storage for tracking rate limits as no storage 
was explicitly specified. This is not recommended for production use. See: 
https://flask-limiter.readthedocs.io#configuring-a-storage-backend for 
documentation about configuring the storage backend.
     warnings.warn(
   INFO  [alembic.runtime.migration] Context impl PostgresqlImpl.
   INFO  [alembic.runtime.migration] Will assume transactional DDL.
   ERROR [flask_migrate] Error: Can't locate revision identified by 
'17fcea065655'
   Loaded your LOCAL configuration at 
[/app/docker/pythonpath_dev/superset_config.py]
   ```
   
   ### Checklist
   
   - [X] I have searched Superset docs and Slack and didn't find a solution to 
my problem.
   - [X] I have searched the GitHub issue tracker and didn't find a similar bug 
report.
   - [X] I have checked Superset's logs for errors and if I found a relevant 
Python stacktrace, I included it here as text in the "additional context" 
section.


-- 
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: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to