-
Notifications
You must be signed in to change notification settings - Fork 10
chore(deps): bump django from 4.2.25 to 4.2.27 #595
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
base: main
Are you sure you want to change the base?
Changes from 6 commits
c4e9c67
a7d01c2
25f59eb
c1a6632
f334e0b
8e9b27b
9dd8430
08fa0d5
2abbd97
d9fb1b0
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -85,6 +85,14 @@ | |
|
|
||
| TEST = True | ||
|
|
||
| # Disable connection health checks for tests to avoid issues with Django 4.2.26+ | ||
| # Connection health checks can interfere with test database setup/teardown | ||
| for db_config in DATABASES.values(): # noqa: F405 | ||
| db_config["CONN_HEALTH_CHECKS"] = False | ||
| if "TEST" not in db_config: | ||
| db_config["TEST"] = {} | ||
| db_config["TEST"]["CONN_HEALTH_CHECKS"] = False | ||
|
|
||
| # # Database | ||
| # # https://docs.djangoproject.com/en/4.2/ref/settings/#databases | ||
|
Comment on lines
+92
to
97
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Bug: 🔍 Detailed AnalysisThe 💡 Suggested FixEnsure 🤖 Prompt for AI AgentDid we get this right? 👍 / 👎 to inform future reviews. |
||
| # DATABASES = { | ||
|
|
||
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
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.
Bug: Health check fix missing from API test settings
The
CONN_HEALTH_CHECKS = Falsefix was applied only toshared.django_apps.settings_test, butcodecov.settings_test(used for API tests) follows a different import chain throughsettings_dev→settings_base→db_settings, which does not include this override. If Django 4.2.26+ connection health checks interfere with test database setup/teardown as the comment indicates, API tests could still experience these issues since they inherit the defaultCONN_HEALTH_CHECKS = Truefromdb_settings.