peter 86bc008a81 fix: a crashed job's crash line carries its job id ...

The bind sat inside the try, so it was already reset when the crash line and the cleanup were logged — the one line most worth finding by job id had none.

2026-09-17 03:53:29 +02:00

..

alembic

feat: Settings → Diagnostics, a consented log level and the tab's own log

2026-09-17 02:42:12 +02:00

app

fix: a crashed job's crash line carries its job id

2026-09-17 03:53:29 +02:00

tests

fix: a crashed job's crash line carries its job id

2026-09-17 03:53:29 +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

chore(lint): set ruff line-length 100 and gate ruff format --check

2026-08-23 07:42:42 +02:00