Commit Graph
68 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
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 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 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 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 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 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 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 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
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
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 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
ricoroma 53eb38e19b Revert "revert: measure scaling-improvement baseline without the pool change"
This reverts commit 62fa57535e.
2026-10-11 15:04:46 +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 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 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 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 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 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