Лабораторная 2 — фактический прогон
Дата: 2026-10-30
Среда: Docker Desktop 29.8.2; Docker VM ARM64, 8 CPU, 4 106 604 544 bytes RAM; лимиты отдельных сервисов не заданы.
Образы: python:3.12.8-slim-bookworm@sha256:2199a62885a12290dc9c5be3ca0681d367576ab7bf037da120e564723292a2f0; postgres:16.4-bookworm; valkey/valkey:8.0.1-alpine.
Python packages в работающем API совпали с requirements.txt: argon2-cffi 23.1.0, bindings 26.1.0, cffi 2.1.1, pycparser 3.12, psycopg/binary 3.2.3, psycopg-pool 3.3.3, redis 5.2.1, typing_extensions 4.16.0.

make check
PASS: offline skeleton structure, local refs and Python syntax; application NOT tested.

docker compose --env-file .env config --quiet
PASS (exit 0)

docker compose --env-file .env up -d --build
PASS; API, PostgreSQL and Valkey reported healthy. API published only on 127.0.0.1:8080.

make test BASE_URL=http://127.0.0.1:8080
PASS: lab2 public API scenario; infrastructure and grading evidence remain separate.

make track2
PASS. Full plans, six write trials, row counts, backup and restore timings are in track2-results.json.
Seed: 100,000 messages; 80,000 in one large chat and 20,000 across 200 small chats.
Restore: separate PostgreSQL 16.4 process/service and persistent restore_data volume.

make quality BASE_URL=http://127.0.0.1:8080
PASS: registration race returned exactly 1 HTTP 201 and 11 HTTP 409; invalid chat creation left no chat row.
EXPLAIN (ANALYZE, BUFFERS): Index Only Scan using messages_history_keyset; 50 rows; Execution Time 0.046 ms; Heap Fetches 0.

make test-dependencies BASE_URL=http://127.0.0.1:8080
PASS: Valkey outage fell back to PostgreSQL; PostgreSQL outage returned bounded HTTP 503 and recovered with the same session.

make test-persistence ACTION_SCRIPT=scripts/restart.sh BASE_URL=http://127.0.0.1:8080
PASS: persistence preserved confirmed data and existing session after restarting API, PostgreSQL and Valkey; volumes retained.

make test-ttl BASE_URL=http://127.0.0.1:8080 (SESSION_TTL_SECONDS=2, temporary Compose env file)
PASS: session expired at the configured two-second TTL. The regular .env was restored to SESSION_TTL_SECONDS=3600 and the final smoke passed again.
