domverse/photoanalyzer
1
0
Fork 0
Code Issues 5 Pull Requests Actions Packages Projects 1 Releases Wiki Activity

US07-04 — Prove Concurrency and Crash Recovery #41

New Issue
Open
opened 2026-07-13 13:10:53 +02:00 by domverse · 0 comments
domverse commented 2026-07-13 13:10:53 +02:00
Owner
Copy Link

Source specification: delivery_backlog/stories/US07-04-fault-concurrency.md

US07-04 — Prove Concurrency and Crash Recovery

Epic: E07

As an operator, I want randomized race and fault tests so concurrency cannot produce
deadlocks, stale commits, duplicate terminal states, or data loss.

Acceptance criteria

  • Test control points exist at persisted transitions without exposing production
    mutation APIs.
  • Tests cover database pressure, worker claim races, file changes, thumbnail races,
    safety/analysis races, EXIF/upload races, rename/archive conflicts, and cancellation.
  • Faults cover process death, disk full, read-only paths, DB busy/corruption, network
    failures, malformed providers, GPU exhaustion, subprocess hangs, and missing tools.
  • Recovery is deterministic or enters an explicit manual-recovery state.

Automated tests

  • Randomized suites repeat with recorded seeds and assert invariants after restart.
  • CI retains journals, logs, DB, seed, and filesystem manifest for any failure.

Dependencies

  • US07-02, US07-03
Source specification: [delivery_backlog/stories/US07-04-fault-concurrency.md](https://git.domverse-berlin.eu/domverse/photoanalyzer/src/branch/main/delivery_backlog/stories/US07-04-fault-concurrency.md) # US07-04 — Prove Concurrency and Crash Recovery Epic: [E07](https://git.domverse-berlin.eu/domverse/photoanalyzer/src/branch/main/delivery_backlog/E07-hardening-release.md) As an operator, I want randomized race and fault tests so concurrency cannot produce deadlocks, stale commits, duplicate terminal states, or data loss. ## Acceptance criteria - Test control points exist at persisted transitions without exposing production mutation APIs. - Tests cover database pressure, worker claim races, file changes, thumbnail races, safety/analysis races, EXIF/upload races, rename/archive conflicts, and cancellation. - Faults cover process death, disk full, read-only paths, DB busy/corruption, network failures, malformed providers, GPU exhaustion, subprocess hangs, and missing tools. - Recovery is deterministic or enters an explicit manual-recovery state. ## Automated tests - Randomized suites repeat with recorded seeds and assert invariants after restart. - CI retains journals, logs, DB, seed, and filesystem manifest for any failure. ## Dependencies - US07-02, US07-03
domverse added this to the E07 — Hardening and Release milestone 2026-07-13 13:10:53 +02:00
domverse added the area/testingpriority/criticaltype/hardeningarea/backend labels 2026-07-13 13:10:53 +02:00
domverse added a new dependency 2026-07-13 13:11:32 +02:00
#39 US07-02 — Harden API Authorization and Path Boundaries
domverse added a new dependency 2026-07-13 13:11:32 +02:00
#40 US07-03 — Harden Media and Metadata Edge Cases
domverse added a new dependency 2026-07-13 13:11:33 +02:00
#42 US07-05 — Deliver Backup and Operational Recovery
domverse added a new dependency 2026-07-13 13:11:33 +02:00
#43 US07-06 — Validate Performance and Resource Bounds
domverse added a new dependency 2026-07-13 13:11:35 +02:00
#44 US07-07 — Automate Full Release Acceptance
domverse added this to the Photo Analyzer Delivery project 2026-07-13 13:19:48 +02:00
domverse added the status/backlog label 2026-07-13 13:52:56 +02:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
area/backend
Backend services, jobs, or API
 area/database
Schema, persistence, migration, or queries
 area/filesystem
Filesystem identity, mutation, or storage
 area/frontend
Browser UI and client-side application
 area/integration
External tools or provider integrations
 area/testing
Automated test suites, fixtures, and tooling
 priority/critical
Release-blocking safety or correctness
 priority/high
Important phase outcome
 priority/normal
Normal planned work
 status/backlog
Awaiting dependency eligibility or prioritization
 status/blocked
Cannot proceed without an explicit resolution
 status/done
Merged, tested, and completed
 status/in-progress
Currently being implemented
 status/ready
Eligible to be claimed
 status/review
Submitted in a pull request for review
 type/feature
User-facing or domain capability
 type/hardening
Security, resilience, operations, or release hardening
 type/migration
Donor extraction, migration, or legacy consolidation
 type/test
Automated test infrastructure or acceptance coverage
No Label area/backend area/testing priority/critical status/backlog type/hardening
Milestone
No items
No Milestone E07 — Hardening and Release
Projects
Clear projects
No project Photo Analyzer Delivery
Assignees
Clear assignees
domverse
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Blocks
#42 US07-05 — Deliver Backup and Operational Recovery
domverse/photoanalyzer
#43 US07-06 — Validate Performance and Resource Bounds
domverse/photoanalyzer
#44 US07-07 — Automate Full Release Acceptance
domverse/photoanalyzer
Depends on
#39 US07-02 — Harden API Authorization and Path Boundaries
domverse/photoanalyzer
#40 US07-03 — Harden Media and Metadata Edge Cases
domverse/photoanalyzer
Reference: domverse/photoanalyzer#41
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?