peter a5fae489e0 test: a request that raises is rolled back, as production rolls it back ...

The shared test session kept whatever a failing handler flushed and never
committed, so a later read in the test saw a write production loses when
get_db closes the session — and a handler whose failure path must commit
(E16: the tracker's issue link) looked right without the commit.

2026-09-19 22:48:20 +02:00

..

alembic

feat(diagnostics): the issue composer — draft, review, screenshots, zip export (E16 S3)

2026-09-19 22:26:49 +02:00

app

feat(diagnostics): the issue composer — draft, review, screenshots, zip export (E16 S3)

2026-09-19 22:26:49 +02:00

tests

test: a request that raises is rolled back, as production rolls it back

2026-09-19 22:48:20 +02:00

alembic.ini

test: the gate's output carries no noise to hide a real warning in

2026-09-17 03:03:37 +02:00

docker-compose.test.yml

test(infra): fail-loud DB/ffmpeg lane + client/as_user/make_user fixtures (E1 S2, TEST-4)

2026-08-18 01:23:06 +02:00

Dockerfile.test

build(deps): pin a reproducible lock + pip-audit; bump node 20->22 (E1 S4, SEC-5/DX-3)

2026-08-18 02:34:45 +02:00

entrypoint.sh

feat: one structured log for every process, with a request id

2026-09-16 01:37:02 +02:00

pytest.ini

test(infra): fail-loud DB/ffmpeg lane + client/as_user/make_user fixtures (E1 S2, TEST-4)

2026-08-18 01:23:06 +02:00

requirements-dev.txt

test: the gate's output carries no noise to hide a real warning in

2026-09-17 03:03:37 +02:00

requirements.lock

feat(downloads): a Facebook cookie download stuck at "Cannot parse data" is retried as Chrome

2026-09-13 22:48:21 +02:00

requirements.txt

fix(downloads): E11.5 epic-end review round 1

2026-09-14 00:50:05 +02:00

ruff.toml

fix(logs): deep-review round 1 — say each failure once, and scrub it everywhere

2026-09-18 03:16:15 +02:00