catborise b24746c1cb fix(logs): blocking a blocked user writes no row; one upload submit path ... Follow-ups from the review of the audit log layers: - Blocking a user who is already blocked, or unblocking one who is not, changes nothing and now writes no row, like any other edit that changes nothing. - write_chunk takes the request instead of the user and an optional request; the view always had one, so the branch only tests used is gone and every chunk 0 goes through the same audited submit. - Tests: a busy clone creates no job and its row carries the page's message; a later chunk that fails writes no submit row; libvirt refusing a network or pool delete is a failed row.		2026-10-23 14:23:32 +03:00
..
__init__.py	test: each app keeps its tests in a tests package	2026-10-12 15:17:30 +03:00
test_audit_rows.py	fix(logs): blocking a blocked user writes no row; one upload submit path	2026-10-23 14:23:32 +03:00
test_tombstones.py	test: each app keeps its tests in a tests package	2026-10-12 15:17:30 +03:00
test_user_create.py	test: each app keeps its tests in a tests package	2026-10-12 15:17:30 +03:00
test_user_update_next.py	test: each app keeps its tests in a tests package	2026-10-12 15:17:30 +03:00
test_views.py	feat(logs): admin changes and logins are recorded on the Logs page	2026-10-23 10:30:48 +03:00