-
-
Notifications
You must be signed in to change notification settings - Fork 225
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.
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
Flask-Migrate fails with flask version 2.1.3 #475
Comments
I'm not aware of any incompatibilities, and I don't see this error here. Can you share the output of |
Thanks @miguelgrinberg for responding, Attaching output of aiohttp==3.8.1 |
Regarding not seeing error, the above attached is actually the entire stack trace. Please let me know if can provide any other details. |
Are you sure you don't have an invalid or outdated alembic_versions table in your database? I just don't see this error here, not sure what it might be, but there is some sort if issue between alembic and your database. |
Thanks @miguelgrinberg, will have a look but don't think there's anything wrong with it as we never update the values manually in alembic_versions table. |
We are using Flask-Migrate(version 3.1.0) from a long time and it used to work fine with our previous flask version BUT after upgrading our Flask version to 2.1.3 it's producing the below error on any
flask db
commandThe error appears on all
The error is being raised from a function named
_revision_for_ident
in dependency alembic BUT not sure what can be the cause of it and have no idea about how we can get it fixed.The text was updated successfully, but these errors were encountered: