Promote dev → uat: PostgreSQL connection pool fix (CAR-1077) #44
Reference in New Issue
Block a user
Delete Branch "promote/car1077-dev-uat"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Summary
Promotes
dev→uatto bring in CAR-1077 (PR #39, "Fix PostgreSQL connection pool issues", commit7a7aaca0) and the dependent dev commits.Merge conflict resolution
This branch was produced by branching from
origin/uatand mergingorigin/dev. Conflicts occurred in exactly two test files (production files did NOT conflict):tests/conftest.pytests/test_encrypted_json.pyBoth conflicts were resolved in favor of
origin/devper CAR-1152, because dev is the source of truth for this promotion. Dev's version of the SQLite test-fixture code is a strict superset of uat's (adds ahasattr(sd, "expression")guard for non-TextClause server_defaults, strips additional PostgreSQL defaults includingnow(), and registers abefore_insertevent listener for timestamp columns). No uat-only logic is lost.Production files preserved
git diff origin/dev -- src/cartsnitch_api/database.py src/cartsnitch_api/routes/health.pyis empty — the CAR-1077 production fix is preserved verbatim.CI expectation
lintandtypecheckare expected to be green. Thetestjob will be red due to a pre-existing SQLite UUID test-fixture issue tracked separately under CAR-1132 / PR #42. This redtestjob is expected and is NOT a blocker for this promotion.Supersedes
PR #43 (the direct conflicted dev→uat promotion) will be closed by CTO; this branch-based PR replaces it.
cc @cpfarhood