Commit Graph
127 Commits
Author SHA1 Message Date
ricoromaandClaude Opus 5.5 ebf080a6a3 docs: archive strict-id-validation
Its delta specs were synced into api-conventions, chats and pagination
during apply and match the main specs.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-16 13:20:35 +03:00
ricoromaandClaude Opus 5.5 3328450805 docs: fix decode_cursor docstring found in verify
The docstring said every field is checked for the server's notation;
only i is, t is checked for type, and unknown fields are ignored. Also
note in tasks.md that the re-encoding check of 3.3 was replaced in 7.2
and fix the rules table. Behaviour of 8fe467a is unchanged; lint and
make test_isolated passed again (138 + 4).

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-16 13:20:00 +03:00
ricoromaandClaude Opus 5.5 f0e3d69570 docs: record strict-id-validation checks
Save the red run on c5d5a1a, the checks of the first fix (628b5f2) and
of the cursor field checks that replaced re-encoding (8fe467a): isolated
tests, rolling update, smoke and own tests through the load balancer
with no 5xx, fault checks, and a clean clone in a temporary compose
project on other ports. Update REPORT.md with the new evidence row, the
behaviour change for non-canonical UUIDs and the current test counts,
and AGENTS.md with the change and the code map.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-16 13:17:00 +03:00
ricoromaandClaude Opus 5.5 8fe467ace0 fix: check cursor fields instead of re-encoding
628b5f2 accepted a cursor only if re-encoding the parsed key gave the
same string. That closed the format both ways: any encoding change, even
a compatible one (an optional field, key order, to_rfc3339 shared with
API responses), would turn cursors issued by a replica of the other
version into 400 during make rolling_update, which the tests cannot see.

decode_cursor now checks the fields one by one: v must be exactly the
integer 1, t and i must be strings, i must be in the server's notation
(lowercase 8-4-4-4-12). Unknown fields are ignored, so a tampered cursor
is still a 400 while the format stays open for compatible changes. The
rule records how to change the format: a new CURSOR_VERSION, with both
versions accepted while replicas are replaced.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-16 13:11:57 +03:00
ricoromaandClaude Opus 5.5 628b5f2278 fix: reject tampered cursors and non-canonical UUIDs
decode_cursor checked only for KeyError, TypeError and ValueError, so a
server-issued cursor whose item id was replaced with [], {}, 123 or
false crashed UUID() with AttributeError and answered 500. It now checks
the types of "t" and "i" before parsing and accepts only the exact
string the server would issue for the parsed key: re-encoding must give
the received cursor, so v=true, an extra field or the id in another
notation is a 400 instead of a page.

pydantic's UUID also accepts ids without hyphens, with the urn:uuid:
prefix and in braces, wider than the contract's format: uuid. chat_id in
the path of the three chat endpoints and member_ids elements now use
UuidIn, which requires the 8-4-4-4-12 form in any case. Response models
and the OpenAPI schema are unchanged.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-16 12:58:30 +03:00
ricoromaandClaude Opus 5.5 c5d5a1ab25 test: cover tampered cursors and UUID input forms
Add black-box tests for the strict-id-validation change: a server-issued
cursor with one field changed (non-string or non-canonical item id,
v=true, extra field) on both lists, member_ids with values of other JSON
types, a non-array member_ids and other UUID notations, and chat_id in
the path of the three chat endpoints. Sync the change's delta specs into
api-conventions, chats and pagination so the coverage check knows the
new scenarios.

The cursor and UUID-notation tests fail on the current code by design;
the fix follows in the next commit.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-16 12:51:16 +03:00
ricoroma 40f470f5b4 docs: update REPORT.md with PR link and commit verification details 2026-10-13 23:40:50 +03:00
ricoromaandClaude Opus 5.5 994dd10c64 docs: archive fix-known-issues and sync its specs
The change moves to openspec/changes/archive/2026-10-13-fix-known-issues.
Its delta requirements join the main specs: graceful-shutdown "Остановка
во время старта", load-benchmark "События Docker профилей отказа и
замены", student-tests "Доказательства исключений сверки в репозитории"
and "PostgreSQL стенда отказов без аварийных перезапусков". AGENTS and
REPORT now say all eight lab 3 changes are archived and none is active.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-13 19:52:08 +03:00
ricoromaandClaude Opus 5.5 69f17a03f3 docs: record the checks of the fix-known-issues verify fixes
Evidence section "Правки по verify": stop-at-start under system Python
3.9.6, cache-check with and without --require-test-keys, auth-storage,
the postgres log read failure path, student tests, failure checks and
the quick failover and rollout profiles on f02694e. The REPORT header
lists what changed after the clean clone commit.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-13 19:50:07 +03:00
ricoromaandClaude Opus 5.5 f02694e102 docs: update expected test counts and notes after fix-known-issues verify
REPORT: 133 and 129 + 4 in the clean clone section, the postgres log
summary of failure_checks, the isolated count on the final code.
AGENTS: do not copy lab 3 evidence, cache-check --require-test-keys.
script-failures: the closed KNOWN_ISSUES entry points to decision 7.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-13 18:23:23 +03:00
ricoromaandClaude Opus 5.5 8be58ce046 fix: bound docker events shutdown in failover and rollout profiles
stop_stream terminates the events CLI, waits 10 s and kills it after
that. The rollout profile starts k6 inside the try, so a k6 start
failure no longer leaves the project events stream running.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-13 18:23:23 +03:00
ricoromaandClaude Opus 5.5 1758790e5c fix: name postgres log read failures in failure checks
docker compose logs runs with check=False; a non-zero exit prints
"postgres log unavailable" and fails the run instead of being reported
as a setup failure.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-13 18:23:23 +03:00
ricoromaandClaude Opus 5.5 824676be32 fix: require test database keys and tidy stop-at-start in the driver
cache-check gains --require-test-keys: without keys of the test database
it fails instead of passing, and a plain PASS now says the temporary
database was not checked. The coverage exclusion names the flag.
auth-storage logs in only the first user, as the design says.
stop-at-start installs its signal handlers right before the try that
restores them and kills docker logs -f when reading is interrupted.
The student-tests rule warns that copied evidence keeps the check green.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-13 18:23:23 +03:00
ricoromaandClaude Opus 5.5 d90a34b88b docs: repeat the clean clone check on the fixed code
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-13 18:02:20 +03:00
ricoromaandClaude Opus 5.5 8fa12f56f7 docs: close the known issues fixed by fix-known-issues
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-13 17:54:29 +03:00
ricoromaandClaude Opus 5.5 949bea4222 docs: collect cache and auth evidence on the lab 3 stand
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-13 17:37:46 +03:00
ricoromaandClaude Opus 5.5 f241126981 test: require evidence files behind coverage exclusions
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-13 17:36:33 +03:00
ricoromaandClaude Opus 5.5 5372d2066c feat: collect cache and auth storage facts with driver commands
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-13 17:34:23 +03:00
ricoromaandClaude Opus 5.5 edad1fda2b fix: exit at once on SIGTERM before the server starts
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-13 16:53:15 +03:00
ricoromaandClaude Opus 5.5 f6052f6c30 fix: stop starting replicas with the compose grace period in the driver
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-13 16:51:25 +03:00
ricoromaandClaude Opus 5.5 42e6edf420 feat: add a driver command that stops a starting replica
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-13 16:50:18 +03:00
ricoromaandClaude Opus 5.5 f8c81878cb fix: run the fault stand postgres under an init process
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-13 16:45:25 +03:00
ricoromaandClaude Opus 5.5 249b67e8c0 test: fail fault checks when the stand postgres crashes
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-13 16:43:54 +03:00
ricoromaandClaude Opus 5.5 b37c45cbb8 revert: drop the failover events cross-check
This reverts commit a24832c.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-13 16:39:44 +03:00
ricoromaandClaude Opus 5.5 a24832c72b test: cross-check failover events against the daemon buffer
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-13 16:16:31 +03:00
ricoromaandClaude Opus 5.5 fe75fcf8a9 fix: stream docker events during failover phases
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-13 16:16:11 +03:00
ricoromaandClaude Opus 5.5 18238588b4 fix: record a zero swap-out delta in bench passports
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-13 16:15:25 +03:00
ricoromaandClaude Opus 5.5 628bbfa639 docs: propose fix-known-issues change
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-13 16:13:04 +03:00
ricoromaandClaude Opus 5.5 f74a3f384e docs: quantify the docker events buffer margin in known issues
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-13 15:28:34 +03:00
ricoromaandClaude Opus 5.5 669a0d9df7 docs: repeat the clean clone check on the final code
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-13 15:19:51 +03:00
ricoromaandClaude Opus 5.5 6476b1e673 docs: track label logs referenced by the report
The *.log rule kept LB, rollout script and 5xx logs of committed
labels out of git while REPORT.md cites them. The 59 logs (556 KB)
hold no tokens, passwords or host paths; quick-* labels stay ignored.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-13 15:18:00 +03:00
ricoromaandClaude Opus 5.5 dbb91507ed docs: note local-only label logs in the report
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-12 19:29:17 +03:00
ricoromaandClaude Opus 5.5 3416ca16b9 docs: archive profile-resources and sync its specs
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-12 19:28:03 +03:00
ricoromaandClaude Opus 5.5 2514ff177d docs: address profile-resources verify findings
Report the failover ranges strictly over phases 1-5 with phase 06
apart, add per-window memory peaks to the failover table, describe
which intervals the window maximum covers, and note the per-second
rows and per-request zeros of the taken labels fixed in f34cb9a.
Record the design findings, the raw logs ignored by git as a known
issue, and the checks after the fixes.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-12 19:26:18 +03:00
ricoromaandClaude Opus 5.5 f34cb9af5c fix: label per-second rows around pause by their unfrozen part
The samples.csv row of an interval that touches the start of a freeze
now gets the window of its unfrozen part, as the window aggregates do
since the thaw correction. CPU per successful request is no longer
computed for a container absent from the window. The definitions in
the summary describe which intervals the window maximum covers.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-12 19:23:29 +03:00
ricoromaandClaude Opus 5.5 c5752962f6 docs: report CPU and memory of failover and rollout profiles
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-12 19:04:33 +03:00
ricoromaandClaude Opus 5.5 9c4249d8d1 docs: add rollout resources label
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-12 18:57:42 +03:00
ricoromaandClaude Opus 5.5 309a00da2a docs: add failover resources label
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-12 18:35:27 +03:00
ricoromaandClaude Opus 5.5 2d267bfbe6 fix: attribute replica CPU around pause to the unfrozen part
A sample interval that crosses docker pause or unpause carried the CPU
spent before the pause and the burst after unpause into the failover
window by proportional split. Use the pause and unpause moments from
Docker events so that interval CPU lands outside the frozen span.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-12 18:09:05 +03:00
ricoromaandClaude Opus 5.5 6505b5e929 feat: sample CPU and memory in failover and rollout profiles
Run bench/sampler.sh in a new scan mode (cgroup walk, no network, no
psql or LB polling) for the whole load of the failover and rollout
profiles. bench/resources.py turns the samples into per-window CPU,
throttling and memory of every component and the VM, with
samples.csv, resources.csv and summary sections; CPU per successful
request only in steady windows. Check the peak CPU budget before the
stand starts.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-12 17:42:04 +03:00
ricoromaandClaude Opus 5.5 417fdd2f22 docs: propose profile-resources change
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-12 17:22:14 +03:00
ricoromaandClaude Opus 5.5 8f007f7bab docs: add network and ports, p50 latency and README compose commands to the report
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-12 16:49:08 +03:00
ricoromaandClaude Opus 5.5 7f00128fbe docs: address final report review and remove PLAN.md
Fix the findings of the final REPORT.md review: prerequisites, the
defence scenario, swap sources, the single explanation of the R* drop
at PostgreSQL 0.5 CPU, known defects in the limitations, a dead link,
stale counts and references. Remove the device name from evidence.

Remove the lab plan now that every change is archived: its decisions
live in REPORT.md and the archived designs, live references point
there, and AGENTS.md drops the transitional section.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-11 22:20:22 +03:00
ricoromaandClaude Opus 5.5 b0637addea fix: run the make instances driver on system python3 3.9
datetime.UTC exists only since Python 3.11, so make instances failed on
the macOS system python3 listed in the report prerequisites. Use
timezone.utc and postponed annotations instead.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-11 22:20:22 +03:00
ricoromaandClaude Opus 5.5 063eedbc71 docs: complete lab 3 report and add final clean clone check
Fill the remaining report sections: clean clone run with versions and
prerequisites, lab 2 carry-over, transaction boundaries, teacher
agreements, skeleton variable mapping, rubric cross-check, experiment
overview, limitations summary, sources and AI usage. Record the clean
clone run of every documented command on default ports.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-11 21:53:13 +03:00
ricoromaandClaude Opus 5.5 67b4303a0a docs: archive scaling-improvement and sync its specs
Sync load-benchmark (series comparison table, track 1 before/after
rules, db4 series) and service-configuration (default pool 10 + 0)
into the main specs, move the change to the archive and drop it from
the transitional state in AGENTS.md.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-11 21:38:16 +03:00
ricoromaandClaude Opus 5.5 25f1962021 docs: address scaling-improvement verify findings
Fix the two-step threshold (x1.118), CPU-per-request spread and
PostgreSQL ranges in REPORT.md and design, record the LB side check
(lb_chkdown, error_codes) in evidence, add the db4 series to the
load-benchmark delta, refresh AGENTS.md, bench.md, PLAN.md and
proposal, and log the swapouts_delta passport defect.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-11 21:36:21 +03:00
ricoromaandClaude Opus 5.5 cb984c1d8d docs: count the pool improvement for track 1 with a recorded caveat
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-11 21:11:19 +03:00
ricoromaandClaude Opus 5.5 dee571c9cd docs: compare scaling-improvement result against the same-session A/A
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-11 21:11:19 +03:00
ricoromaandClaude Opus 5.5 adbb06d8f9 docs: report second scaling-improvement attempt for track 1
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-11 17:51:55 +03:00