Files
DongHyeonkaandClaude Opus 5 b2963105a8 docs(keycloak-session-store): import the session-storage lab as a new project
The keycloak project ended with four open questions that design could not
settle. A two-VM lab was built to answer them by measurement, and this is
that material: 26 experiments, 125 raw command outputs, 22 browser captures.

Follows the import procedure in README.md.

  source/     the originating repository verbatim — 78 documents, 28 SVGs,
              8 manifests, plus .source-revision recording the commit
  final/      the SSOT
    document.md   729 lines written from the 29 experiment documents, not
                  concatenated: what was predicted, what was measured, and
                  where the measurement itself was wrong
    evidence/raw    125 outputs, flattened to <experiment>__<file> because
                    the originals collided (01-baseline.txt appeared three
                    times) and the audit only globs the top level
    evidence/meta   one per raw file; command and exitCode are null and the
                    README says why rather than inventing them
    evidence/browser  22 captures
    assets/       three diagrams through techviz
    .techviz/     their VizSpecs

A separate project rather than an addition to keycloak: the B-layer answers
that project's four questions, but the A, C and D layers are about cluster
failure, SSO and operations, and one document.md should hold one subject.
The four question records there can point here through 관계.

Recorded rather than papered over: only three of the 28 diagrams were
remade. The repository forbids hand-drawn SVG and forbids titles inside the
canvas; all 28 originals carry both, so converting them is redrawing, not
reformatting. They stay in source/ and the gap is written into the document.

verify-pipeline.py passes. audit-records.py reports no issues.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
2026-09-04 22:51:59 +09:00

32 lines
1.6 KiB
Java

package dev.caskeleton.adapter.outbound.persistence.postgresql.error;
import static org.assertj.core.api.Assertions.assertThat;
import dev.caskeleton.adapter.outbound.persistence.api.PersistenceOperationName;
import dev.caskeleton.adapter.outbound.persistence.api.error.ConstraintCode;
import dev.caskeleton.adapter.outbound.persistence.api.transaction.RetryProfile;
import dev.caskeleton.adapter.outbound.persistence.api.transaction.TransactionAttempt;
import dev.caskeleton.adapter.outbound.persistence.transaction.DefaultJpaRetryPolicy;
import java.sql.SQLException;
import java.time.Duration;
import java.time.Instant;
import org.junit.jupiter.api.Test;
class PostgreSql40003PolicyProbeTest {
@Test
void currentTranslatorDemotes40003BeforeRetryPolicy() {
var translator = PostgreSqlExceptionTranslator.with(name -> new ConstraintCode("unknown.constraint"));
var translated = translator.translate(
new SQLException("completion unknown", "40003"),
new PersistenceOperationName("probe.40003"), 1, Duration.ZERO, "trace-probe");
var decision = DefaultJpaRetryPolicy.forProfile(
RetryProfile.boundedContention("probe-default", 3))
.classify(translated, TransactionAttempt.first(Instant.EPOCH));
System.out.println("translated.category=" + translated.category());
System.out.println("translated.completionUnknown=" + translated.completionUnknown());
System.out.println("decision.disposition=" + decision.disposition());
System.out.println("decision.reason=" + decision.reason());
assertThat(decision.disposition().name()).isEqualTo("FAIL");
}
}