🤖 Refactor Database Initialization for Celery Workers #1623
+32
−4
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
👋 Hi there! This PR was automatically generated by Autofix 🤖
This fix was triggered by Rohan Agarwal
Fixes SEER-9P
This pull request introduces changes to the database initialization process for Flask applications, specifically for scenarios where Celery workers are involved. The
init_celery_app
function inapp.py
has been updated to include a new parameterskip_db_init
, which, when set, skips the database initialization step during bootup. In theinitialize_database
function withindb.py
, a global variable_db_initialized
is introduced to track whether the database has already been initialized, preventing redundant initialization attempts. Additionally, thebootup
function now checks for an application context before invokinginitialize_database
, ensuring appropriate context management in worker environments.If you have any questions or feedback for the Sentry team about this fix, please email autofix@sentry.io with the Run ID: 2255.