🤖 Enhance Database Initialization with Thread Safety and Logging #1737
+25
−3
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
![sentry-autofix[bot]](https://avatars.githubusercontent.com/in/801464?s=60&v=4){kind=small}
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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 thread safety and logging enhancements to the database initialization process in the application. In 'src/celery_app/app.py', debug logging is added to track the Celery worker's database connection status. In 'src/seer/db.py', a threading lock is introduced to prevent concurrent database initialization, ensuring that initialization occurs only once. The existing initialization code is modified to check if the database has already been initialized, and if so, it ensures that the session is correctly bound. Exception handling is added to reset the initialization flag upon failure. Finally, in 'src/seer/bootup.py', debug statements are added to log the progress of the database initialization.
If you have any questions or feedback for the Sentry team about this fix, please email autofix@sentry.io with the Run ID: 3126.