ЛР 3 — БВТ2301 — Сафронов — на 5, трек 1 #6

Closed
ricoroma wants to merge 127 commits from ricoroma/mtusi2026lab3-safronov:solution/bvt2301-safronov into main
127 Commits
Author SHA1 Message Date
ricoromaandClaude Opus 5.5 ce89eba22d docs: record the clean clone check of ebf080a
Repeat the REPORT.md "Запуск из чистого clone" sequence from a real git
clone of the final strict-id-validation code on the default ports: env
setup, stand, no-cache build, check, validate, smoke, instances on two
Python versions, persistence, failover of each replica and kill, own
tests, fault checks and the isolated run. All steps exit 0. The clone ran
as compose project mtusi-lab3-cleancheck while the working stand was
only stopped, because removing its volume was refused by the agent's
auto mode; the previous checks ran as mtusi-lab3.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-16 13:32:33 +03:00
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
ricoromaandClaude Opus 5.5 4648cd0a8c docs: add second scaling-improvement attempt comparisons and checks
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-11 17:51:55 +03:00
ricoromaandClaude Opus 5.5 17998c92ce docs: add scaling-db-nooverflow2 label
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-11 17:48:32 +03:00
ricoroma 7a38c5dbcc Revert "revert: measure scaling-improvement baseline again without the pool change"
This reverts commit 5c07923d8c.
2026-10-11 17:23:34 +03:00
ricoroma de6001c526 docs: add scaling-db-before2 bench evidence 2026-10-11 17:23:34 +03:00
ricoromaandClaude Opus 5.5 45a0ad723b docs: add second scaling db A/A label for scaling-improvement
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-11 16:58:20 +03:00
ricoromaandClaude Opus 5.5 5c07923d8c revert: measure scaling-improvement baseline again without the pool change
This reverts commit 53eb38e (the pool change 9c3959d, 623a973, 80e64cd).

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-11 16:30:27 +03:00
ricoromaandClaude Opus 5.5 a676a520b0 docs: plan the second scaling-improvement measurement attempt
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-11 16:30:27 +03:00
ricoromaandClaude Opus 5.5 056ca19a53 docs: format probe script in connection cost evidence
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-11 15:46:34 +03:00
ricoromaandClaude Opus 5.5 8b69913995 docs: report scaling-improvement pool result for track 1
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-11 15:46:24 +03:00
ricoromaandClaude Opus 5.5 1694b1d0ae docs: add scaling-improvement comparisons, connection cost and checks
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-11 15:46:13 +03:00
ricoromaandClaude Opus 5.5 cd88b48b41 docs: add scaling-db-nooverflow label
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-11 15:30:47 +03:00
ricoroma 53eb38e19b Revert "revert: measure scaling-improvement baseline without the pool change"
This reverts commit 62fa57535e.
2026-10-11 15:04:46 +03:00
ricoroma dfd9ecce29 docs: add scaling-db-before bench evidence 2026-10-11 15:04:46 +03:00
ricoromaandClaude Opus 5.5 3df111cd80 docs: add scaling db A/A label for scaling-improvement
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-11 14:37:29 +03:00
ricoromaandClaude Opus 5.5 62fa57535e revert: measure scaling-improvement baseline without the pool change
This reverts commits 9c3959d, 623a973 and 80e64cd.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-11 14:10:43 +03:00
ricoromaandClaude Opus 5.5 1bb8ea67ad feat: add two-cell db4 series for the scaling-improvement measurements
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-11 14:06:57 +03:00
ricoromaandClaude Opus 5.5 80e64cda4a test: count PostgreSQL sessions without healthcheck and flush races
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-11 13:46:39 +03:00
ricoromaandClaude Opus 5.5 623a973dac test: wait for PostgreSQL session stats before counting pool reconnections
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-11 13:30:38 +03:00
ricoromaandClaude Opus 5.5 9c3959d768 perf: keep a fixed PostgreSQL pool without overflow connections
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-11 13:25:26 +03:00
ricoromaandClaude Opus 5.5 0b0421ad2f docs: record track 1 improvement hypothesis H4
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-11 13:23:49 +03:00
ricoromaandClaude Opus 5.5 1e50a4a3fc feat: compare PostgreSQL sessions and connections in track 1 series
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-11 13:23:12 +03:00
ricoromaandClaude Opus 5.5 029aa3be82 docs: propose scaling-improvement change
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-11 13:19:56 +03:00
ricoromaandClaude Opus 5.5 bbd6f65316 chore: archive scaling-bench change
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-11 12:25:18 +03:00
ricoromaandClaude Opus 5.5 dedb8ba0fa docs: report PostgreSQL saturation series db and rubric answer
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-11 12:24:17 +03:00
ricoromaandClaude Opus 5.5 195a3f8ad9 docs: add series db plots and host check
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-11 12:22:45 +03:00
ricoromaandClaude Opus 5.5 9fbe2ea503 feat: draw series db in R* plot and summarize PostgreSQL saturation
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-11 12:22:32 +03:00
ricoromaandClaude Opus 5.5 48d10dad37 docs: add scaling series db
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-11 12:21:04 +03:00
ricoromaandClaude Opus 5.5 46e8f75a2c docs: record series db calibration in scaling-bench design
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-11 11:31:39 +03:00
ricoromaandClaude Opus 5.5 95539a1883 feat: add track 1 series db with a tight PostgreSQL CPU limit
Configs may carry a fifth element, the PostgreSQL CPU limit, which goes
into the config key (-pg<CPU>), the budget and the cell stand. Series db:
1, 2, 4 replicas at the tight limit and a 4 x 1 control at 2 CPU; label
summaries show PostgreSQL CPU at R* against its limit and throttling.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-11 11:27:30 +03:00
ricoromaandClaude Opus 5.5 a3279374f7 docs: fix scaling-bench verify findings in report, design and rules
Close the 53300 known issue, restate H1 and saturation conclusions
against the pre-registered criteria and grid resolution, name the
unresolved host mechanism, attribute overload 503 to the pool timeout,
and plan a fresh A/A for scaling-improvement.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-11 07:36:33 +03:00
ricoromaandClaude Opus 5.5 4abedaed78 docs: add 53300 evidence, regression and regenerated track 1 summaries
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-11 07:35:49 +03:00
ricoromaandClaude Opus 5.5 dcea85942a feat: add cost and memory tables, passports and sampler limits to track 1 outputs
plots.py summary gains per-request CPU by component, PostgreSQL waits and
pool, H1b throttling and memory peaks; compare.py and plots.py headers
name the spec, change and host; errors logs match 5xx by status field and
keep the exception tail; series labels record sampler limits.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-11 07:26:36 +03:00
ricoromaandClaude Opus 5.5 68edc66742 fix: answer 503 when PostgreSQL refuses connections with too many clients
SQLSTATE 53300 (too_many_connections) joins UNAVAILABLE_SQLSTATES, so a
refused pool connection gives 503 unavailable instead of 500. New fault
check fills max_connections through the failure stand hook and expects
503 in the contract format.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-11 07:26:36 +03:00
ricoromaandClaude Opus 5.5 ca0817390f docs: report track 1 scaling series
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-11 06:49:49 +03:00
ricoromaandClaude Opus 5.5 0ea787ccae docs: add scaling-bench plots and comparisons
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-11 06:49:03 +03:00
ricoromaandClaude Opus 5.5 bfc5eb8ede docs: add scaling A/A label
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-11 06:48:19 +03:00
ricoromaandClaude Opus 5.5 0479789aa3 docs: add scaling series plots for A and B
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-11 06:26:38 +03:00
ricoromaandClaude Opus 5.5 7b6a31b62a docs: record 500 instead of 503 on too many clients found by the pool series
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-11 06:26:30 +03:00
ricoromaandClaude Opus 5.5 b7e787a658 fix: move reference line labels off the bars in the scaling plots
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-11 06:26:03 +03:00
ricoromaandClaude Opus 5.5 f65a8e86d1 docs: add scaling pool series
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-11 06:26:03 +03:00
ricoromaandClaude Opus 5.5 1320584d9f docs: add scaling series B
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-11 06:01:52 +03:00
ricoromaandClaude Opus 5.5 3401388b5e docs: describe track 1 series in AGENTS.md
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-11 04:47:04 +03:00
ricoromaandClaude Opus 5.5 71359be0fb docs: add scaling series A
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-11 04:47:04 +03:00
ricoromaandClaude Opus 5.5 cbe3b4a43b docs: add scaling-bench self-checks
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-11 04:10:02 +03:00
ricoromaandClaude Opus 5.5 712d2450e4 fix: preallocate all k6 VUs in track 1 steps so the generator does not drop iterations near R*
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-11 03:55:21 +03:00
ricoromaandClaude Opus 5.5 68eef77119 fix: put the growth series end label above its whisker in the R* plot
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-11 03:45:46 +03:00
ricoromaandClaude Opus 5.5 5de4da997c fix: drop the resume image warning, the containerd image id changes on every build
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-11 03:44:41 +03:00
ricoromaandClaude Opus 5.5 02fd3d8a36 feat: add track 1 scaling series to the bench stand
Series a/b/pool/ab/quick in bench/run.py: per-cell fresh stand with the
configuration's replicas and max_connections, open-model mixed profile
(k6/mixed.js), fixed levels and R* search by SLO, a sampler container
for cgroup, VM, HAProxy and PostgreSQL metrics, resume and a stand
lock. Pure helpers in bench/scaling.py, SVG plots in bench/plots.py,
series mode for bench_compare and bench_ab. Hypotheses H1-H3 go to
REPORT.md before the first series.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-11 03:28:36 +03:00
ricoromaandClaude Opus 5.5 525ace7c9b docs: propose scaling-bench change
Track 1 "cost of scaling": open-model series A (fixed 4 CPU budget),
B (1-6 replicas), pool border (max_connections 100 vs 50) and A/A,
sampler of cgroup/VM/LB/PostgreSQL metrics, generator limits, series
mode for bench_compare and bench_ab. Hypotheses H1-H3 are recorded in
the design before any series run.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-11 02:48:40 +03:00
ricoromaandClaude Opus 5.5 84ee13ca5a chore: archive rolling-update change
Sync the rolling-update delta specs into db-migrations,
graceful-shutdown, load-balancing and load-benchmark, move the change to
the archive, mark it in PLAN.md and update the transitional state and
code map in AGENTS.md.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-11 01:59:19 +03:00
ricoromaandClaude Opus 5.5 6f85d21f3b docs: retake rolling-update evidence on the final verify commit
Re-run the compatibility walk-through, the script failure cases with a
real Ctrl+C through a pseudo-terminal, the stand lifecycle after
replacement and the quick rollout and failover self-checks on 84161c0
with a clean tree; update the report rows and limitations.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-11 01:56:30 +03:00
ricoromaandClaude Opus 5.5 84161c033a fix: keep migration lock timeout below the app statement timeout
With lock_timeout equal to statement_timeout (5 s) every request queued
behind a migration waiting for its lock failed with 503 together with
the migration. A 2 s lock timeout lets the queue proceed once the
migration gives up.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-11 01:38:10 +03:00
ricoromaandClaude Opus 5.5 5e102e6d0c fix: harden rolling update cleanup and preconditions found in verify
Reset the new replica ID before entering the starting state and let the
cleanup find a replica created by an interrupted compose scale; refuse
to start while LB slots keep a manual drain or maint state; log the exit
code of each stopped old replica and print full LB commands for manual
cleanup. Document the migrate step and the rollback tag limitation.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-11 01:33:33 +03:00
ricoromaandClaude Opus 5.5 69ebf5cd38 docs: add rolling-update baseline measurement and report
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-11 01:21:34 +03:00
ricoromaandClaude Opus 5.5 9dcea0b2b8 docs: add rolling-update regression evidence and report sections
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-11 01:17:34 +03:00
ricoromaandClaude Opus 5.5 de654a1c83 fix: recreate the migrate service container during rolling update
A one-off run --rm left the migrate container of the previous image in
the stand; scripts/restart.sh then started it as a dependency of api and
the old migrations failed on the newer schema, so test-persistence broke.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-11 01:04:50 +03:00
ricoromaandClaude Opus 5.5 5403464cfb docs: add rolling-update compatibility and script failure evidence
Old image passes smoke and student tests on the new schema, rolling
update, rollback and roll forward under tests/load.py give zero failed
requests; the run_docker known issue is not reproduced and is closed.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-11 01:01:33 +03:00
ricoromaandClaude Opus 5.5 d2148ac566 feat: add rolling update with LB drain and rollout load profile
scripts/rolling-update.sh (make rolling_update) replaces API replicas one
by one: build, migrations once, new replica UP in HAProxy, old replica
drained and put into maintenance through the LB runtime API on loopback,
then stopped and removed; the slot is reset once DNS drops the address.
Expand migration adds messages.instance_id with a lock timeout. The bench
rollout profile runs the same script under constant load, starting from
the image of an older commit built with git archive.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-11 00:49:50 +03:00
ricoromaandClaude Opus 5.5 9a00795de1 docs: propose rolling-update change
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-11 00:26:36 +03:00
ricoromaandClaude Opus 5.5 c50b7211b8 chore: archive graceful-failover change
Delta specs synced into graceful-shutdown, load-balancing, load-benchmark
and service-configuration; the change moves to
openspec/changes/archive/2026-10-11-graceful-failover/. PLAN.md marks the
change archived and AGENTS.md notes what was handed to rolling-update.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-11 00:10:35 +03:00
ricoromaandClaude Opus 5.5 fc715b74d4 docs: add LB rule of bench_compare to graceful-failover delta
The verify fix in bench/compare.py refuses a label measured without the
load balancer; the load-benchmark delta now modifies the label comparison
requirement accordingly.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-11 00:08:13 +03:00
ricoromaandClaude Opus 5.5 f38a56c4ea docs: retake graceful-failover checks after verify
The rejected LB pool variant is re-measured on committed code with a
temporary second HAProxy differing in http-reuse only: the replica, not
the LB, closed the last idle connection after 60.4 s. Exploratory
never/safe SIGTERM numbers are separated from evidence. hang-key cleanup
is shown under Ctrl+C and SIGTERM, bench_compare refuses a label without
the LB. Drain before SIGTERM and the run_docker recreate issue are handed
to rolling-update in PLAN.md and KNOWN_ISSUES.md; design gains decision 10.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-11 00:07:21 +03:00
ricoromaandClaude Opus 5.5 12783aaff1 fix: harden graceful-failover checks found in verify
hang-key names its trigger per run, turns SIGTERM and SIGHUP into an
interrupt so the trigger is always dropped and the replica unpaused, and
prints the cleanup SQL if dropping fails. idle-conns reports who closed
the idle connections and can read the pool of another LB container, so a
variant LB config can be checked against the same replicas. bench_compare
refuses a label measured without the load balancer. Stale numbers removed
from the haproxy.cfg comment.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-11 00:00:54 +03:00
ricoromaandClaude Opus 5.5 4234df5767 docs: add graceful-failover evidence and report
Failover profile label baseline from 459f84c on a checked host: stop and
kill of each replica under 200 req/s give 0 errors and LB exclusion in
0.79-1.81 s (bound 2.5 s), pause gives LB exclusion in 5.83-6.00 s
(bound 6.5 s) with 504s for half the requests and recovery in 6 s;
reconciliation of retried writes matches. Evidence for detection,
keep-alive (LB closes idle replica connections at 10.1 s) and the hung
replica key lock, regression checks, timeout chain and level 4 rows in
REPORT.md.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-10 23:52:47 +03:00
ricoromaandClaude Opus 5.5 459f84c75c feat: coordinate timeout chain and add failover load profile
HAProxy checks get fastinter 500ms and timeout check 2.5s (hung replica
detected within 6.5 s), http-reuse never with uvicorn keep-alive 60 s so
the LB closes idle replica connections, and app connections set
idle_in_transaction_session_timeout so a frozen replica releases its
idempotency key. The bench stand runs behind HAProxy with N replicas and
gains the failover profile (make bench_failover / bench_failover_quick):
constant-rate writes with a key and reads while each replica is stopped,
killed or paused, with per-second timeline, detection and recovery time
and write reconciliation. Driver commands idle-conns and hang-key check
the keep-alive and hung-transaction decisions.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-10 23:21:12 +03:00
ricoromaandClaude Opus 5.5 b76a666621 docs: propose graceful-failover change
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-10 22:32:12 +03:00
ricoromaandClaude Opus 5.5 aec6f23cb0 chore: archive replicas-lb change
Main specs were already in sync with the deltas (sync re-run, no
changes). PLAN.md marks stage 2 archived and points graceful-failover
at the corrected detection formula; AGENTS.md notes what of the timeout
chain is measured so far and the new replicas evidence.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-10 22:10:31 +03:00
ricoromaandClaude Opus 5.5 cb14586a19 docs: retake replicas-lb evidence from a4ca9ef after verify
The stand was recreated from a4ca9ef (make down, make run_docker) and
all evidence of the change was taken again on it: stand, distribution,
LB errors, test-persistence, test-failover for each replica (stop and
kill), stop-one refusals, make test and student_test through the LB,
test_isolated, failure_checks and bench self-checks.

New evidence closes scenarios verify found without proof: a real git
clone on non-default ports, a hung replica (docker pause: DOWN after
7.7 s, in-flight request 504), PostgreSQL outage behind the LB, replica
tests failing against one process, aborted responses via
driver.py kill-inflight. REPORT.md gets the corrected detection
formula, the measured cost of the 1 CPU limit for Argon2id and the new
rows.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-10 22:09:15 +03:00
ricoromaandClaude Opus 5.5 a4ca9ef3a7 fix: correct replicas-lb details found in verify
- stop-one.sh: an empty TARGET_INSTANCE_ID now exits 2 in any shell,
  as the design states (${VAR:?} gave 1 under bash).
- driver.py kill-inflight: reproducible "aborted response is not
  retried" scenario (logins in flight, replica killed via stop-one.sh).
- Detection time of a hung replica is fall x (inter + timeout check) =
  8 s, not inter x fall + timeout check = 5 s (docker pause: 7.3 s);
  fixed in haproxy.cfg, balancer.md and the design.
- The 1 CPU replica limit is kept on purpose; the compose comment and
  the design now say that Argon2id uses more and logins are slower.
- load-balancing spec: API_REPLICAS is read by compose and Makefile.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-10 18:44:57 +03:00
ricoromaandClaude Opus 5.5 de93056eab docs: add replicas-lb evidence and report
Evidence from 4e0cc4e: stand ports, limits and per-service env,
X-Instance-Id distribution and scaling, LB-generated errors,
test-persistence through the LB, test-failover for each replica in stop
and kill modes, stop-one refusals, test runs and bench self-checks.
REPORT.md gains the LB architecture, timeout chain, limits, criteria
rows and defence answers. Coverage exclusions for restart now point to
the lab 3 persistence evidence; stale lab 2 pointers go to
KNOWN_ISSUES.md.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-10 18:31:18 +03:00
ricoromaandClaude Opus 5.5 4e0cc4e965 fix: start DNS-resolved replicas down until checks pass
Without init-state down HAProxy marked a slot UP as soon as Docker DNS
returned the container address, before uvicorn listened, so requests
after LB restart or scale-up hit a replica that was not ready.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-10 18:08:50 +03:00
ricoromaandClaude Opus 5.5 ab71c3b51e feat: put API replicas behind HAProxy
HAProxy 3.4 is the only published entry point; api runs as
API_REPLICAS replicas without ports, found through Docker DNS and
checked on /health/ready. Retries only on connection failure, LB errors
in the contract error format, resource limits and per-service secrets.
Adds scripts/stop-one.sh, LB-aware restart.sh, make replicas /
instances / lb_stats and replica tests driven by EXPECT_REPLICAS.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-10 18:05:05 +03:00
ricoromaandClaude Opus 5.5 8e15e02898 docs: propose replicas-lb change
HAProxy as the single entry point, API replicas without published
ports, resource limits and per-service secrets, restart and stop-one
hooks, replica tests in student-tests.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-10 17:40:04 +03:00
ricoromaandClaude Opus 5.5 b5ae252254 chore: archive instance-id-idempotency change
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-10 17:23:41 +03:00
ricoromaandClaude Opus 5.5 c5840bfaa8 docs: add idempotency and X-Instance-Id evidence to the report
- evidence for replay, conflict, replay through a new API process and
  after restarting API and storages, keys table, key race,
  X-Instance-Id in responses and logs, explicit and invalid
  instance_id and key TTL, test runs
- stand evidence: make wipe_data leaves the lab 2 volume intact, build
  from a fresh git clone passes smoke, bench restore stage sends with
  Idempotency-Key
- REPORT.md: X-Instance-Id, idempotency design, IDEMPOTENCY_TTL_SECONDS
  mapping, limitations and evidence rows
- tasks.md: mark the change tasks done, add follow-ups from verify

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-10 17:08:47 +03:00
ricoromaandClaude Opus 5.5 af4bca08c9 feat: carry lab 2 over and add X-Instance-Id and idempotency keys
- carry the lab 2 solution over and plan lab 3 (PLAN.md, OpenSpec
  change instance-id-idempotency)
- rename the compose project to mtusi-lab3 and the image to :lab3
- add X-Instance-Id to every response and instance_id to every log
  record ([app] instance_id, hostname by default)
- require Idempotency-Key on POST messages: keys table in Postgres,
  key and message in one transaction, replay returns the same 201,
  another body gets 409, TTL from [idempotency] ttl_seconds
- send the key from student-tests, k6 scenarios and the skill driver;
  add idempotency, X-Instance-Id, key race and fault tests

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-08 19:42:36 +03:00