[GitHub] [superset] pomegranited commented on issue #17991: Flask-Migrate output is not logged during alembic migrations

[GitBox <gi...@apache.org>]

pomegranited commented on issue #17991:
URL: https://github.com/apache/superset/issues/17991#issuecomment-1379761557

   I'm having this issue too, when initializing superset `2.0.1`. Running `superset db upgrade` fails with error code 1, but with no logging information as to why, which makes it pretty hard to figure out what's going on. cf https://stackoverflow.com/a/74474278
   
   When I apply the changes in this PR to the `alembic.ini` file, `superset db upgrade` then logs the flask-migrate error, which I was then able to resolve manually, cf https://stackoverflow.com/a/67015509
   
   ```
   ERROR [flask_migrate] Error: Can't locate revision identified by '4ce1d9b25135'
   ```
   Can this PR be merged so that others who may encounter errors with flask-migrate can see them?


-- 
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