Files
document-haness/docs/clean-architecture-backend-template/final/evidence/raw/148-fileserver-suite-verification.txt
T
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

44 lines
1.6 KiB
Plaintext

Scope adapter-outbound-fileserver - focused suite verification at HEAD
revision=a24ece9cf797f7ea647e33bf846b115208ed1ba5
generatedAt=2026-08-30T01:35:12+00:00
=== First run: container default locale ===
$ ./gradlew :adapter:outbound:fileserver:test
LocalPersistentPayloadOperationsTest > inspectsLegacyRootArtifactByBoundedNoFollow
StreamingWithoutRewritingIt() FAILED
java.nio.file.InvalidPathException: Malformed input or input contains unmappable
characters: 월간 export -- legacy 01.csv
at java.base/sun.nio.fs.UnixPath.encode(UnixPath.java:129)
at LocalPersistentPayloadOperationsTest.java:331
398 tests completed, 1 failed, 3 skipped
=== Cause: the analysis container has no UTF-8 locale ===
$ locale 2>&1 | head -4
LANG=
LANGUAGE=
LC_CTYPE="POSIX"
LC_NUMERIC="POSIX"
exit=0
$ java -XshowSettings:properties -version 2>&1 | grep -iE 'sun.jnu|file.encoding|native.encoding'
file.encoding = UTF-8
native.encoding = ANSI_X3.4-1968
sun.jnu.encoding = ANSI_X3.4-1968
exit=0
sun.jnu.encoding=ANSI_X3.4-1968 cannot encode the Korean file name the test uses, so
Path.resolve throws before any adapter code runs. The failure is in the test fixture's
own path construction (line 331), not in a production class.
=== Second run: same revision, UTF-8 locale ===
$ docker exec -e LANG=C.UTF-8 -e LC_ALL=C.UTF-8 ... ./gradlew :adapter:outbound:fileserver:test --rerun-tasks
BUILD SUCCESSFUL in 54s
Classification: analysis-environment limitation, not a repository defect.
The same shape was recorded for the JPA scope's PostgreSQL TLS lane (EVD-062 area).
No production or test source was modified to reach the passing run.
$ git status --short | wc -l
0
exit=0