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
Code changes for SQLAlchemy 2.0.x upgrade #946
Conversation
Signed-off-by: Carlo Costino <carlo.costino@gsa.gov>
Signed-off-by: Carlo Costino <carlo.costino@gsa.gov>
Signed-off-by: Carlo Costino <carlo.costino@gsa.gov>
A quick note to folks reviewing this PR: several other dependency updates have been merged in from This was done to keep the PR fresh and in sync with |
Attempted "Send a message from an existing template", the following error happened:
And I received this on the frontend:
Did not receive a text. This happens when I manually type in my phone number rather than pressing the "Use my number" button. Otherwise, everything looks good. All tests run, all came back OK, other than what I noted above. Since it is involved with the sending process, it doesn't seem to matter if you are using an existing template, create a new one, or copy a template first. It does seem to be totally around the step where you can choose to manually enter the phone number. |
Noting this, as I found it during testing, but it seems completely unrelated to this change: While checking the SQLAlchemy update, I found this error on bootup of the api, which might be important:
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I am not able to duplicate the errors I saw now, so they exist, but I can't make them happen. Anyway, the system seems G2G to be merged, everything looks fine.
The startup error I've not been able to duplicate either and is likely the result of a local dev environment setup thing; we won't really know for sure if it's an issue with startup until it's put into one of the other cloud.gov environments, but I'm not seeing any indication that it would be. The personalization error when scheduling a send has already been flagged as a separate issue, so that's also accounted for and not related to this change. It does look like we're good to go here to move forward! |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
A big thank you to @aanand-gsa for all of the hard work making this migration to SQLAlchemy 2.0.x possible for Notify.gov! 🙂 🎉
Thanks @ccostino for the appreciation! It's been a team effort, and I'm glad we could successfully migrate to SQLAlchemy 2.0.x for Notify.gov. 😊 🙌 |
This PR proposes the solution for the breaking changes introduced on SQLAlchemy 2.0 upgrade https://docs.sqlalchemy.org/en/20/changelog/migration_20.html
Details
This changeset addresses all of the changes we need to make to our app and tests in order to upgrade to the 2.0.x series of SQLAlchemy. It builds upon the work we previously completed to upgrade Python to 3.12.x and Flask 3.0.x, and accounts for the remaining dependency updates that are shared between Flask and SQLAlchemy.
Security Considerations