DongHyeonkaandClaude Opus 5
0e61f86eb5
Implements the Stable and Experimental JPA persistence platform designs against real PostgreSQL, adapted to this repository's fail-closed 19-leaf registry. The design models the platform as 25 Gradle projects. `src/settings.gradle` throws unless the registry holds exactly 19 leaves, so the plan's modules become packages inside `:adapter:outbound:persistence-jpa` (starter in `:app-bootstrap`, testkit in its own source set). The full mapping, the renames this repository's naming gate required, and every deliberate substitution are recorded in `docs/jpa/repository-adaptation.md`. Seven Docker-backed lanes replace the plan's seven JVM test suites. Each fails closed: a lane that discovers nothing, or a container that cannot start, is an error rather than a skip. Three defects the contracts found against a real server: - `CommitFailureClassifier` treated only SQLSTATE 40003, class 08, and transport breaks as completion-unknown. A backend terminated mid-commit reports 57P01, and the commit record may already be in the WAL — so a possibly-committed transaction could be re-run. 57P01/57P02/57P03 now classify as completion-unknown. - `SchemaTenantMigrationOrchestrator` recorded `MigrateResult`'s target version, which is empty for a tenant already current, reporting migrated tenants as unmigrated during a partial rollout. It now reads the applied version back from the tenant's schema history. - `JpaStreamExecutor` checked only the declared return type for reactive publishers, and `RegisteredPostgreSqlCopyLoader` passed the COPY timeout to `SET`, which is parsed before parameter binding. `JpaModuleBoundaryTest` enforces the plan's module map as package rules; `verifyCleanArchitectureDependencies` governs edges between leaves and cannot see these. Its first assertion is that the import is non-empty, because every rule under it is a `noClasses()` rule and would pass vacuously on an empty import. Verified: 128 container tests across all seven lanes, 1183 unit tests, `:adapter:outbound:persistence-jpa:check`, `:app-bootstrap:check`, `verifyCleanArchitectureDependencies`, `verifyOneTypePerFile`. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
44 lines
1.7 KiB
YAML
44 lines
1.7 KiB
YAML
# Commit-ambiguity failure injection for the JPA platform (design §39).
|
|
#
|
|
# The suite needs a proxy rather than a kill switch because the scenario that matters cannot be
|
|
# produced any other way. Stopping the container, killing the process, or closing the client socket
|
|
# all break *before* the server commits — the easy case, where the transaction rolled back and the
|
|
# use case may simply be re-run. The hard case is a commit the server completed whose
|
|
# acknowledgement never came back, and it only exists if you can cut the return path while leaving
|
|
# the forward path intact.
|
|
#
|
|
# That is what CommitAmbiguityProxy does with a downstream-only toxic, and it is the one scenario
|
|
# that distinguishes a platform that reports completion-unknown from one that retries a write which
|
|
# already succeeded.
|
|
#
|
|
# Ordinary contract runs use Testcontainers and do not need this file; it exists for reproducing a
|
|
# failure scenario by hand.
|
|
|
|
services:
|
|
postgres:
|
|
image: postgres:16-alpine
|
|
environment:
|
|
POSTGRES_DB: jpa_failure
|
|
POSTGRES_USER: jpa_failure
|
|
POSTGRES_PASSWORD: jpa_failure
|
|
# No published port: the suite must reach PostgreSQL only through the proxy, or the injected
|
|
# fault can be bypassed by connecting directly and the test passes without testing anything.
|
|
expose:
|
|
- "5432"
|
|
healthcheck:
|
|
test: ["CMD-SHELL", "pg_isready -U jpa_failure -d jpa_failure"]
|
|
interval: 2s
|
|
timeout: 3s
|
|
retries: 30
|
|
|
|
toxiproxy:
|
|
image: ghcr.io/shopify/toxiproxy:2.11.0
|
|
depends_on:
|
|
postgres:
|
|
condition: service_healthy
|
|
ports:
|
|
# 8474 is the control API the suite drives; 8666 is the proxied PostgreSQL port.
|
|
- "8474:8474"
|
|
- "8666:8666"
|
|
command: ["-host", "0.0.0.0"]
|