Archive copy must succeed before a packet counts as filed (Gitea issue 57)

FILE checks the archive folder and copies the packet inside the filing transaction. A failed check or copy rolls the filing back, so the packet stays in its previous stage; the person filing gets 503 archive_failed, and in its own transaction the server writes an archive.filing_blocked audit row and raises the critical archive_failed condition to Admin for that packet (who tried, folder, error). The next successful filing clears it. The archive-copy job now only catches up filings made while the archive was off. PLAN question 53, CHANGELOG, FEED and SECURITY updated. Co-Authored-By: Claude Opus 5.5 <[email protected]>
2026-11-03 15:52:09 -07:00
parent 5f8165c833
commit 6adaf7bf25
11 changed files with 254 additions and 98 deletions
@@ -72,7 +72,7 @@ test.describe.serial("archive", () => {
    expect((await packet(clara, p.id)).seal).toBeTruthy();
    await closeAll(clara, wade, wes, andy, quinn);

-    // FILE asks the worker for a copy at once. The Admin section shows it done.
+    // FILE made the copy in the filing transaction (Gitea issue 57). The Admin section shows it done.
    const ann = await admin(browser);
    await expect
      .poll(